Methods and apparatus for service provision to out-of-coverage apparatus in wireless systems

ABSTRACT

Methods and apparatus for provision of resources from one or more devices within a wireless communication network to one or more devices that are outside of the wireless communication network. In one embodiment, the methods and apparatus utilize so-called “quasi-licensed” CBRS (Citizens Broadband Radio Service) wireless spectrum in conjunction with a cellular wireless communication network (e.g. 4G, 5G, or LTE-based) for the delivery of services to a number of installed fixed wireless apparatus (CPE/FWA) at user or subscriber premises. The CPE/FWAs may act as relays and/or supplementation devices to provide service to the CPEs that are out of the network coverage, effectively enabling addition of new customers to the network. As such, additional CAPEX (capital expenditure) on infrastructure is largely avoided.

RELATED APPLICATIONS

The subject matter of this application is generally related to co-ownedand co-pending U.S. patent application Ser. No. 16/676,188 filed Nov. 6,2019 and entitled “METHODS AND APPARATUS FOR ENHANCING COVERAGE INQUASI-LICENSED WIRELESS SYSTEMS,” the foregoing incorporated herein byreference in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of wirelessnetworks and specifically, in one or more exemplary aspects, to methodsand apparatus for “relaying” signals from one or more devices utilizingradio frequency spectrum to provide high-speed data services toout-of-network devices, such as for example those providing connectivityvia technologies such as Citizens Broadband Radio Service (CBRS), LSA(Licensed Shared Access), TVWS, or Dynamic Spectrum Allocation (DSA).

2. Description of Related Technology

A multitude of wireless networking technologies, also known as RadioAccess Technologies (“RATs”), provide the underlying means of connectionfor radio-based communication networks to user devices. Such RATs oftenutilize licensed radio frequency spectrum (i.e., that allocated by theFCC per the Table of Frequency Allocations as codified at Section 2.106of the Commission's Rules. In the United States, regulatoryresponsibility for the radio spectrum is divided between the U.S.Federal Communications Commission (FCC) and the NationalTelecommunications and Information Administration (NTIA). The FCC, whichis an independent regulatory agency, administers spectrum fornon-Federal use (i.e., state, local government, commercial, privateinternal business, and personal use) and the NTIA, which is an operatingunit of the Department of Commerce, administers spectrum for Federal use(e.g., use by the Army, the FAA, and the FBI). Currently only frequencybands between 9 kHz and 275 GHz have been allocated (i.e., designatedfor use by one or more terrestrial or space radio communication servicesor the radio astronomy service under specified conditions). For example,a typical cellular service provider might utilize spectrum for so-called“3G” (third generation) and “4G” (fourth generation) wirelesscommunications as shown in Table 1 below:

TABLE 1 Technology Bands 3G 850 MHz Cellular, Band 5 (GSM/GPRS/EDGE).1900 MHz PCS, Band 2 (GSM/GPRS/EDGE). 850 MHz Cellular, Band 5(UMTS/HSPA+ up to 21 Mbit/s). 1900 MHz PCS, Band 2 (UMTS/HSPA+ up to 21Mbit/s). 4G 700 MHz Lower B/C, Band 12/17 (LTE). 850 MHz Cellular, Band5 (LTE). 1700/2100 MHz AWS, Band 4 (LTE). 1900 MHz PCS, Band 2 (LTE).2300 MHz WCS, Band 30 (LTE).

Alternatively, unlicensed spectrum may be utilized, such as that withinthe so-called ISM-bands. The ISM bands are defined by the ITU RadioRegulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of theRadio Regulations. In the United States, uses of the ISM bands aregoverned by Part 18 of the Federal Communications Commission (FCC)rules, while Part 15 contains the rules for unlicensed communicationdevices, even those that share ISM frequencies. Table 2 below showstypical ISM frequency allocations:

TABLE 2 Frequency range Type Center frequency Availability Licensedusers 6.765 MHz-6.795 MHz A 6.78 MHz Subject to local Fixed service &mobile acceptance service 13.553 MHz-13.567 MHz B 13.56 MHz WorldwideFixed & mobile services except aeronautical mobile (R) service 26.957MHz-27.283 MHz B 27.12 MHz Worldwide Fixed & mobile service exceptaeronautical mobile service, CB radio 40.66 MHz-40.7 MHz  B 40.68 MHzWorldwide Fixed, mobile services & earth exploration-satellite service433.05 MHz-434.79 MHz A 433.92 MHz only in Region amateur service & 1,subject to radiolocation service, local acceptance additional apply theprovisions of footnote 5.280 902 MHz-928 MHz B 915 MHz Region 2 onlyFixed, mobile except (with some aeronautical mobile & exceptions)radiolocation service in Region 2 additional amateur service 2.4 GHz-2.5GHz B 2.45 GHz Worldwide Fixed, mobile, radiolocation, amateur &amateur-satellite service 5.725 GHz-5.875 GHz B 5.8 GHz WorldwideFixed-satellite, radiolocation, mobile, amateur & amateur- satelliteservice   24 GHz-24.25 GHz B 24.125 GHz Worldwide Amateur, amateur-satellite. radiolocation & earth exploration-satellite service (active) 61 GHz-61.5 GHz A 61.25 GHz Subject to local Fixed, inter-satellite,acceptance mobile & radiolocation service 122 GHz-123 GHz A 122.5 GHzSubject to local Earth exploration-satellite acceptance (passive),fixed, inter- satellite, mobile, space research (passive) & amateurservice 244 GHz-246 GHz A 245 GHz Subject to local Radiolocation, radioacceptance astronomy, amateur & amateur-satellite service

ISM bands are also been shared with (non-ISM) license-freecommunications applications such as wireless sensor networks in the 915MHz and 2.450 GHz bands, as well as wireless LANs and cordless phones inthe 915 MHz, 2.450 GHz, and 5.800 GHz bands.

Additionally, the 5 GHz band has been allocated for use by, e.g., WLANequipment, as shown in Table 3:

TABLE 3 Dynamic Freq. Selection Band Name Frequency Band Required (DFS)?UNII-1 5.15 to 5.25 GHz No UNII-2 5.25 to 5.35 GHz Yes UNII-2 Extended5.47 to 5.725 GHz Yes UNII-3 5.725 to 5.825 GHz No

User client devices (e.g., smartphone, tablet, phablet, laptop,smartwatch, or other wireless-enabled devices, mobile or otherwise)generally support multiple RATs that enable the devices to connect toone another, or to networks (e.g., the Internet, intranets, orextranets), often including RATs associated with both licensed andunlicensed spectrum. In particular, wireless access to other networks byclient devices is made possible by wireless technologies that utilizenetworked hardware, such as a wireless access point (“WAP” or “AP”),small cells, femtocells, or cellular towers, serviced by a backend orbackhaul portion of service provider network (e.g., a cable network). Auser may generally access the network at a “hotspot,” a physicallocation at which the user may obtain access by connecting to modems,routers, APs, etc. that are within wireless range.

CBRS and other “Shared Access” Systems—

In 2016, the FCC made available Citizens Broadband Radio Service (CBRS)spectrum in the 3550-3700 MHz (3.5 GHz) band, making 150 MHz of spectrumavailable for mobile broadband and other commercial users. The CBRS isunique, in that it makes available a comparatively large amount ofspectrum (frequency bandwidth) without the need for expensive auctions,and without ties to a particular operator or service provider.Comparable technologies are in development, including for instance DSA,TVWS TV White Space), and LSA (Licensed Spectrum Access).

Moreover, the CBRS spectrum is suitable for shared use betweengovernment and commercial interests, based on a system of existing“incumbents,” including the Department of Defense (DoD) and fixedsatellite services. Specifically, a three-tiered access framework forthe 3.5 GHz is used; i.e., (i) an Incumbent Access tier 102, (ii)Priority Access tier 104, and (iii) General Authorized Access tier 106.See FIG. 1. The three tiers are coordinated through one or more dynamicSpectrum Access Systems (SAS) 202 as shown in FIG. 2 (including e.g.,Band 48 therein).

Incumbent Access (existing DOD and satellite) users 102 includeauthorized federal and grandfathered Fixed Satellite Service (FSS) userscurrently operating in the 3.5 GHz band shown in FIG. 1. These userswill be protected from harmful interference from Priority Access License(PAL) and General Authorized Access (GAA) users. The sensor networks,operated by Environmental Sensing Capability (ESC) operators, make surethat incumbents and others utilizing the spectrum are protected frominterference.

The Priority Access tier 104 (including acquisition of spectrum for upto three years through an auction process) consists of Priority AccessLicenses (PALs) that will be assigned using competitive bidding withinthe 3550-3650 MHz portion of the band. Each PAL is defined as anon-renewable authorization to use a 10 MHz channel in a single censustract for three years. Up to seven (7) total PALs may be assigned in anygiven census tract, with up to four PALs going to any single applicant.Applicants may acquire up to two-consecutive PAL terms in any givenlicense area during the first auction.

The General Authorized Access tier 106 (for any user with an authorized3.5 GHz device) is licensed-by-rule to permit open, flexible access tothe band for the widest possible group of potential users. GeneralAuthorized Access (GAA) users are permitted to use any portion of the3550-3700 MHz band not assigned to a higher tier user and may alsooperate opportunistically on unused Priority Access License (PAL)channels. See FIG. 2A.

The FCC's three-tiered spectrum sharing architecture of FIG. 1 utilizes“fast-track” band (3550-3700 MHz) identified by PCAST and NTIA, whileTier 2 and 3 are regulated under a new Citizens Broadband Radio Service(CBRS). CBSDs (Citizens Broadband radio Service Devices—in effect,wireless access points) 206 (FIG. 2) can only operate under authority ofa centralized Spectrum Access System (SAS) 202. Rules are optimized forsmall-cell use, but also accommodate point-to-point andpoint-to-multipoint, especially in rural areas.

Under the FCC system, the standard SAS 202 includes the followingelements: (1) CBSD registration; (2) interference analysis; (3)incumbent protection; (4) PAL license validation; (5) CBSD channelassignment; (6) CBSD power limits; (7) PAL protection; and (8)SAS-to-SAS coordination. As shown in FIG. 2, these functions areprovided for by, inter alia, an incumbent detection (i.e., environmentalsensing) function 207 configured to detect use by incumbents, and anincumbent information function 210 configured to inform the incumbentwhen use by another user occurs. An FCC database 211 is also provided,such as for PAL license validation, CBSD registration, and otherfunctions.

An optional Domain Proxy (DP) 208 is also provided for in the FCCarchitecture. Each DP 208 includes: (1) SAS interface GW includingsecurity; (2) directive translation between CBSD 206 and domaincommands; (3) bulk CBSD directive processing; and (4) interferencecontribution reporting to the SAS.

A domain is defined is any collection of CBSDs 206 that need to begrouped for management; e.g.: large enterprises, venues, stadiums, trainstations. Domains can be even larger/broader in scope, such as forexample a terrestrial operator network. Moreover, domains may or may notuse private addressing. A Domain Proxy (DP) 208 can aggregate controlinformation flows to other SAS, such as e.g., a Commercial SAS (CSAS,not shown), and generate performance reports, channel requests,heartbeats, etc.

CBSDs 206 can generally be categorized as either Category A or CategoryB. Category A CBSDs have an EIRP or Equivalent Isotropic Radiated Powerof 30 dBm (1 Watt)/10 MHz, fixed indoor or outdoor location (with anantenna <6 m in length if outdoor). Category B CBSDs have 47 dBm EIRP(50 Watts)/10 MHz, and fixed outdoor location only. Professionalinstallation of Category B CBSDs is required, and the antenna must beless than 6 m in length. All CBSD's have a vertical positioning accuracyrequirement of +/−3 m. Terminals (i.e., user devices akin to UE) have 23dBm EIRP (0.2 Watts)/10 MHz requirements, and mobility of the terminalsis allowed.

In terms of spectral access, CBRS utilizes a time division duplex (TDD)multiple access architecture.

FIG. 2B illustrates a typical prior art CBRS-based CPE (consumerpremises equipment)/FWA architecture 200 for a served premises (e.g.,user residence), wherein the CPE/FWA 203 is backhauled by a base station(e.g., eNB) 201. A PoE (Power over Ethernet) injector system 204 is usedto power the CPE/FWA 203 as well as provide Ethernet (packetconnectivity for the CPE/FWA radio head to the home router 205.

Disabilities with CPE Coverage—

Extant CBRS architectures, while useful from many standpoints, currentlylack mechanisms for providing the requisite data-rates to a given CPE(such as a premises Fixed Wireless Access or FWA device) that is outsideof a cell coverage area (and accordingly which receives no downlink (DL)or uplink (UL) signals), as is shown in FIG. 2C. In particular, in thetypical CBRS network, there may be one or more CPE/FWA (e.g., House 3shown in FIG. 2C) that is out of the coverage area or cell 209 of awireless network (e.g., one using CBRS spectrum) due to e.g., path lossand/or interference from being distant from the serving base station,obstruction to line-of-sight between CPEs and base stations,interference from other cells, etc.

In the architecture 220 shown in FIG. 2C, the “out-of-coverage” or OOCpremises is also typically in a more remote area and/or not served byany alternate service provider capability of sufficient bandwidth (e.g.,DOCSIS HFC cable drop, fiber, satellite dish, etc.) such that the use ofthe CBRS wireless backhaul shown is required for delivery of high-speedbroadband services.

One prospective cure to this problem (at least for the DL) is to simplyraise base station transmitter EIRP. A base station such as 3GPP eNB orgNB is limited in data throughput and area coverage in aninterference-limited environment, due to the link budget limitations andthe efficiency of the hardware components of its radio unit(s). Toprovide the requisite high level of performance (consistent with theaforementioned SLA) and greater coverage area, a single base stationserving a CPE/FWA device has to transmit on comparatively higher power.However, such high power operation will violate the radio requirements(e.g., maximum transmit power and spectral masks) enforced in the3GPP/CBRS specifications.

Technologies such as (i) use of a high device antenna gain; (ii) use ofMultiple-Input-Multiple-Output (MIMO) system; (iii) Orthogonal FrequencyDivision Multiplexing (OFDM) (iv) advanced error control coding (e.g.Low Density Parity Check Codes (LDPC) or Turbo codes) are known in theprior arts to increase the throughput and coverage area. All of thesetechniques, while effective and implemented in typical 3GPP-basedsystems underlying CBRS, do not inherently mitigate the effects of thechannel loss and interference, thereby effectively limiting the maximumdata rates that can be achieved under such prior art approaches whileoperating within the aforementioned power limitations.

Hence, to achieve provide service to clients that are out-of-coverage ofexisting systems such as those utilizing CBRS spectrum, improvedapparatus and methods are needed. Such improved apparatus and methodswould ideally support comparatively high levels of performance (e.g.,data rates on both DL and UL) for out-of-coverage CPE/FWA deviceswithout large capital expenditures (CAPEX) to install e.g., additionalbase stations in the coverage area, and/or utilization of (fully)licensed spectrum with prospectively higher transmit power limits.Advantageously, such a solution would effectively add more customers tothe network, thereby potentially lowering the overall cost of operatingthe network and providing services to customers (including potentiallyreduced subscription fees).

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus, for inter alia, “relaying” resources of awireless network to CPE such as FWA devices that are outside of anextant coverage area of the wireless network.

In a first aspect of the disclosure, a method of operating a CPE such asa fixed wireless access (FWA) device is disclosed. In one embodiment,the method includes: causing discovery of a first FWA device that isoutside a coverage area of a wireless network; identifying at least onesecond FWA device within the coverage area of the wireless network andcapable of providing resources to the first FWA device; causingestablishment of a wireless connection to the identified at least onesecond FWA device; and transacting data with the at least one second FWAdevice in order to cause provision of the resources to the first FWAdevice.

In one variant, the discovery includes use of a 3GPP-based D2D(device-to-device) protocol whereby nearby CPE/FWA can discover oneanother, whether by scheduled (Type 2B) or unscheduled (Type 1)approaches.

In another variant, the identifying of the at least one second FWAdevice within the coverage area of the wireless network and capable ofproviding the resources to the first FWA device includes determiningthat a data rate associated with the at least one second FWA deviceexceeds a prescribed service level agreement (SLA) requirement, the SLAbetween a subscriber of a network operator managing the wireless networkand the network operator.

In yet another variant of the method, the method further includes:subsequent to receiving the resources at the first FWA device,conducting, at the first FWA device, an evaluation to determine anadditional capacity that is required to be provided to the FWA device inorder to meet or exceed an SLA associated therewith; receiving data fromrespective ones of a plurality of other FWA devices, the received dataindicating a respective additional capacity capability; and based atleast on the received data and the determined additional capacity,selecting the at least one other FWA device from the plurality of otherFWA devices with which to establish the wireless connection.

In another variant of the method, the identifying at least one secondFWA device capable of providing the resources to the first FWA deviceincludes evaluating data regarding ones of a plurality of other FWAdevices within wireless range of the first FWA device such that adevice-to-device (D2D) connection can be established therebetween.

In a further variant of the method, the first FWA device is configuredto operate within a frequency range between 3.550 and 3.70 GHzinclusive, and the causing establishment of a wireless connection to theidentified at least one second FWA device includes causing a request tobe issued to a SAS (spectrum allocation system) in data communicationwith the wireless network to obtain at least one spectrum grant, atleast one frequency within the at least one spectrum grant beingutilized to establish the wireless connection. In one suchimplementation, the method further includes receiving at the first FWAdevice data relating to the at least one spectrum grant from theidentified at least one second FWA device, and utilizing the receiveddata relating to the at least one spectrum grant in the establishment ofthe wireless connection.

In another such implementation, the method further includes receiving atthe FWA device data relating to the at least one spectrum grant fromanother FWA device within the wireless network, and utilizing thereceived data relating to the at least one spectrum grant in theestablishment of the wireless connection.

In still another implementation, the causing the request to be issued tothe SAS in data communication with the wireless network to obtain the atleast one spectrum grant includes causing the request to be transmittedfrom the first FWA device to the SAS via the at least one second FWAdevice utilizing a sidelink D2D connection between the first FWA deviceand the at least one second FWA device.

In a further implementation, the causing the request to be issued to theSAS in data communication with the wireless network to obtain the atleast one spectrum grant includes causing the request to be initiatedvia the at least one second FWA device.

In another aspect of the disclosure, a computerized method of operatinga first fixed wireless access (FWA) device that is outside a coveragearea of a wireless network is disclosed. In one embodiment, the methodincludes; identifying a second FWA device within the coverage area ofthe wireless network and capable of providing resources to the first FWAdevice; causing establishment of a wireless connection to the identifiedsecond FWA device; and transacting data with the second FWA device inorder to cause provision of the resources to the first FWA device fromthe wireless network via at least the second FWA device.

In one variant, the identifying of the second FWA device within thecoverage area of the wireless network and capable of providing theresources to the first FWA device includes determining that a data rateassociated with the second FWA device exceeds a prescribed threshold orrequirement.

In another variant, the prescribed threshold or requirement isestablished to enable selection of the second FWA device from aplurality or potential candidate FWA devices, and the method furtherincludes: subsequent to receipt of the resources at the first FWAdevice, conducting, at the first FWA device, an evaluation to determinean additional capacity that is required to be provided to the first FWAdevice; receiving data from respective ones of a plurality of other FWAdevices, the received data indicating a respective additional capacitycapability; and based at least on the received data and the determinedrequired additional capacity, selecting the at least one other FWAdevice from the plurality of other FWA devices with which to establish awireless connection.

In yet another variant, the identifying the second FWA device capable ofproviding the resources to the first FWA device includes evaluating dataregarding ones of a plurality of other FWA devices within wireless rangeof the first FWA device such that an inter-device connection can beestablished therebetween. In one implementation, the establishment ofthe inter-device connection includes using 3GPP (Third GenerationPartnership Project) D2D (device to device) protocols between the firstFWA device and at least one other of the plurality of other FWA devices,the D2D protocols including at least synchronization within a CBRS(Citizens Broadband Radio Service) radio frequency band.

In a further variant, the first FWA device is configured to operatewithin a frequency range between 3.550 and 3.70 GHz inclusive, and thecausing establishment of a wireless connection to the identified secondFWA device includes causing a request to be issued to a SAS (spectrumallocation system) in data communication with the wireless network toobtain at least one spectrum grant, at least one frequency within the atleast one spectrum grant being utilized to establish the wirelessconnection. In one implementation thereof, the method further includes:receiving at the first FWA device data relating to the at least onespectrum grant from the identified second FWA device; and utilizing thereceived data relating to the at least one spectrum grant in theestablishment of the wireless connection.

In another implementation of the method, the causing the request to beissued to the SAS in data communication with the wireless network toobtain the at least one spectrum grant includes causing the request tobe transmitted from the first FWA device to the SAS via the at least onesecond FWA device utilizing a sidelink connection between the first FWAdevice and the second FWA device.

In yet another implementation of the method, the causing the request tobe issued to the SAS in data communication with the wireless network toobtain the at least one spectrum grant includes causing the request tobe initiated from the second FWA device.

In still another variant, the causing the discovery of the first FWAdevice includes: causing at least one of the first FWA device or thesecond FWA device to transmit an announcement, the announcementconfigured to indicate to other FWA devices that the at least first orsecond FWA device exists; and based on the announcement by and receiptof at least one response thereto, causing the first FWA device to senddata to the at least one second FWA device to cause the establishment ofthe wireless connection.

In another aspect of the disclosure, computerized premises apparatus foruse in a wireless network is described. In one embodiment, the apparatusincludes: at least one wireless interface; processor apparatus in datacommunication with the at least one wireless interface; and storageapparatus in data communication with the processor apparatus.

In one variant, the storage apparatus comprises at least one computerprogram configured to, when executed by the processor apparatus: engagein communication with at least one wireless access device viautilization of a direct synchronization and discovery protocol, the atleast one wireless access device within in wireless range of (i) the atleast one wireless interface of the computerized premises apparatus and(ii) at least one base station; obtain first data from the at least onewireless access device enabling establishment of a first wirelessconnection, the first wireless connection between the computerizedpremises apparatus and the at least one wireless access device; utilizethe at least one wireless access device to request a resource grantusing the at least one base station; and based at least on a criterionrelating to performance or capability of the at least one FWA devicebeing exceeded, receive resources in accordance with the resource grantfrom the at least one FWA device.

In one implementation, the computerized premises apparatus and the atleast one wireless access device each comprise a FWA (fixed wirelessaccess) device configured to operate in a CBRS (citizens broadband radioservice) frequency band, and the at least one base station includes a3GPP-compliant NodeB (NB) configured to operate in a CBRS frequencyband.

In another implementation, the at least one computer program is furtherconfigured to, when executed by the processor apparatus: determine thatthe first connection cannot meet a prescribed performance levelrequirement associated with the computerized premises apparatus based onthe resources received from the at least one wireless access device; andbased at least on the determination, cause a communication with at leastone second wireless access device within wireless range of thecomputerized premises device to request supplementation of the wirelessconnection via a second wireless connection, the communication torequest supplementation including data relating to an amount ofbandwidth supplementation required by the computerized premisesapparatus.

In one configuration, the at least one computer program is furtherconfigured to, when executed by the processor apparatus: utilize atransport layer process to enable aggregation of data packetstransmitted to the computerized premises apparatus via the wirelessconnection and the second wireless connection when the wirelessconnection and the second wireless connection have been established.

In another configuration, the determination that the first connectioncannot meet the prescribed performance level requirement associated withthe computerized premises apparatus includes determination of the amountby a performance determination process operative to execute on thecomputerized premises apparatus, the determination process configured tomeasure at least one parameter related to data rate or throughput of theat least one wireless interface while utilizing the wireless connection.

In another variant of the computerized premises apparatus, theengagement includes utilization of a 3GPP D2D (Device to Device)protocol based on a schedule provided to at least the at least onewireless access device by the at least one base station.

In a different variant, the engagement includes utilization of a 3GPPD2D (Device to Device) protocol based on a discovery protocol initiatedby the computerized premises apparatus.

In a further aspect of the disclosure, computer readable apparatusincluding a non-transitory storage medium, the non-transitory mediumincluding at least one computer program having a plurality ofinstructions is disclosed. In one embodiment, the plurality ofinstructions are configured to, when executed on a processing apparatus:receive first data relating to a measurement of at least one firstperformance metric relating to a first wireless connection between afirst computerized premises apparatus and a first base station, thefirst wireless connection used to provide first resources to the firstcomputerized premises apparatus; and based on the at least oneperformance metric exceeding a first prescribed threshold, causeestablishment a second wireless connection between the firstcomputerized premises apparatus and a second computerized premisesapparatus, the second wireless connection utilized for a provision ofsecond resources to the second computerized premises apparatus.

In one variant, the plurality of instructions are configured to, whenexecuted on the processing apparatus: receive second data relating to ameasurement of at least one performance metric relating to the secondwireless connection; receive third data relating to a measurement of atleast one performance metric relating to a third wireless connectionbetween a third computerized premises apparatus and either the firstbase station or a second base station; and based at least on (i) thesecond data indicating that the at least one second performance metricdoes not meet a second prescribed threshold, and (ii) the third dataindicating that the at least one performance metric exceeds a thirdprescribed threshold, cause establishment of a fourth wirelessconnection between the first computerized premises apparatus and thethird computerized premises apparatus, the fourth wireless connectionutilized for a provision of third resources to the second computerizedpremises apparatus, the third resources supplementing the first andsecond resources such that the least one second actual performancemetric at least meets the second prescribed threshold.

In another variant, the second computerized premises apparatus includesa FWA device that is (i) completely out of a coverage area of the firstand second base stations and (ii) configured to operate in a CBRS(citizens broadband radio service) frequency band; the first and secondbase stations each comprise a 3GPP-compliant NodeB (NB) configured tooperate in a CBRS frequency band; and each of the wireless connectionseach comprise operation in an RRC_Connected state.

In another aspect of the disclosure, computerized method of operating afixed wireless access (FWA) device within a wireless network, isdisclosed. In one embodiment, the method includes discovering a firstFWA device that is outside a coverage area of the wireless network;transmitting performance data associate with a second FWA device to acomputerized resource allocation process, the computerized resourceallocation process configured to grant an amount of resources to thefirst FWA device; and based on receipt of the grant of the amount of theresources from the computerized resource allocation process, provide theamount of the resources to the first FWA device, thereby connecting thefirst FWA device to the wireless network via the second FWA device.

In one variant, the method further includes establishing adevice-to-device (D2D) connection with first FWA device based on thediscovery thereof. In one implementation, the D2D connection is based ona Type 2B D2D semi-persistent UE-specific allocation approach.

In yet another aspect of the disclosure, a method of operating awireless network infrastructure is disclosed. In one embodiment, themethod includes using one or more “relay” CPE disposed within a wirelessnetwork to provide data bandwidth to a target CPE disposed outside ofthe coverage of the fixed infrastructure of the wireless network.

In one variant, MSO customers with such relay or primary CPE/FWA(“anchor customers”) within a given area may be given a differentiatedset of services, privileges, subscription rates, or other features(including differentiated equipment capabilities/configurations) so asto incentivize such customers for maintaining the primary or relay CPE.For instance, in one implementation, primary or relay CPE are selectedbased on geographical/topological/signal propagation considerations,including proximity to one or more xNBs within the infrastructure, suchthat maximal impact or relay performance is enabled with respect to thelargest possible number of other out-of-coverage subscribers.

In an additional aspect of the disclosure, computer readable apparatusis described. In one embodiment, the apparatus includes a storage mediumconfigured to store one or more computer programs, such as on a fixedwireless receiver of a managed wireless network. In one embodiment, theapparatus includes a program memory or HDD or SDD and stores one or morecomputer programs supporting relaying of data from a serving basestation and the recipient fixed wireless receiver via one or more otherfixed wireless receivers.

In another aspect, methods and apparatus for communication coordinationfor delivery/receipt of wireless signals to/from one or more targetCPE/FWA are disclosed. In one embodiment, the communication coordinationincludes data messaging between the one or more serving CPE/FWA and thefirst target CPE/FWA such that the signals associated with one or moreserving devices may be used to provide services to the first targetdevice.

In another aspect of the disclosure, methods and apparatus fordifferentiated spectrum allocation are described. In one embodiment, themethods and apparatus are configured to allocate one type or performancelevel of spectrum to one entity, and a second type/performance level ofspectrum to another entity, based on e.g., the relationship of the twoentities. For example, in one variant, a first CPE/FWA acting as aprimary or relay device may request and/or be unilaterally allocated PALspectrum, while a secondary CPE/FWA being served by the first isallocated GAA spectrum.

In yet a further aspect, improved proximity-based methods and apparatususeful within e.g., a quasi-licensed wireless system are disclosed.

In another aspect, methods and apparatus useful within e.g., aquasi-licensed wireless system for providing packet aggregation insupport of multiple physical bearers utilizing a multi-stream capableprotocol such as Stream Control Transmission Protocol (SCTP) aredisclosed. In one variant, the protocol is non-blocking so as to avoide.g., head of the line queuing of data packets and latency associatedtherewith.

In still a further aspect, methods and apparatus useful within e.g., aquasi-licensed wireless system for providing device to device (D2D)communication in support of relay or supplementation functions aredisclosed.

In a further aspect, methods and apparatus for “repurposing” a D2Dconnection between two devices are disclosed. In one embodiment, the twodevices include MSO-provided CBRS-enabled FWA, wherein the establishedD2D is used to supplement one of the FWA's from at least the other FWA.

In another aspect, network controller apparatus for enabling provisionof services to out-of-coverage CPE is disclosed. In one embodiment, thecontroller is part of an MSO wireless network infrastructure. In onevariant, the controller is integrated with or part of a 3GPP 5GC or EPC,and is communicative with logical processes on two or more CPE apparatus(via interposed RAN including Node B apparatus) to obtain performancedata for scheduling/allocating network resources and the provision ofservices to out-of-coverage CPE.

In yet further aspects of the disclosure, methods and apparatus for bothadding new customers to a service provider network without significantCAPEX are disclosed. In one embodiment, extant CPE and supportinginfrastructure are configured to extend wireless coverage to new orincipient CPE to be added to the network which cannot otherwise beserviced by the infrastructure.

In yet another aspect, a multi-role CPE apparatus is disclosed. In oneembodiment, the multi-role apparatus is configured to operate as both aCBRS FWA (i.e., consumer and low power transmitter of wireless data forsupport of broadband services to the CPE itself) in one role, and alsoas a higher-power CBSD and provider of services to one or moreout-of-coverage CPE in a second role. In some variants, the roles may beintermixed, such as where the multi-role CPE operates in one frequencyband (e.g., using one sector of its antennae) for communication with aserving base station, and another sector/sectors and/or frequency bandsto communicate with the one or more OOC devices, including at powerlevels commensurate with classification/registration as a CBSD.

In yet another aspect, methods and apparatus for providing wirelessservice to an OOC CPE are disclosed. In one embodiment, the methods andapparatus utilize a first in-coverage or primary CPE using a first typeof spectrum to provide service to the OOC CPE and, when the OOC CPEdetermines that it requires additional capacity from the primary CPE,requests such additional capacity. When the primary CPE (or networkentity such as EPC or 5GC or MSO controller) determines that the primaryCPE cannot provide the requested additional capacity using the firsttype of spectrum, utilization of a second type of spectrum is used bythe primary CPE for at least its backhaul to its serving BS). In onevariant, the first type of spectrum is CBRS GAA spectrum, and the secondtype is PAL, the latter having ostensibly much less interference due toits quasi-licensed status (at least for the duration of the grant of thePAL spectrum).

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a graphical illustration of prior art CBRS (Citizens BroadbandRadio Service) users and their relationship to allocated frequencyspectrum in the 3.550 to 3.700 GHz band.

FIG. 2 is a block diagram illustrating a general architecture for theCBRS system of the prior art.

FIG. 2A is a graphical representation of allocations for PAL versus GAAusers within the frequency band of FIG. 2.

FIG. 2B is a graphical illustration of a prior art configuration fordelivery of data from a base station to an end-user device (CPE/FWA)within the wireless coverage areas of the base station.

FIG. 2C is a graphical illustration of a prior art configuration fordelivery of data from a base station to end-user devices (CPE/FWA)within the wireless coverage areas of the base station, and an exemplarypremises (House 3) outside of the wireless coverage areas of the basestations.

FIG. 3A is a graphical illustration of an exemplary configuration for“relaying” network resources to an out-of-coverage (OOC) CPE/FWA,according to one embodiment of the present disclosure.

FIG. 3B shows the exemplary configuration for “relaying” networkresources to the out-of-coverage CPE/FWA of FIG. 3A, with detail of theCPE/FWA components of each premises.

FIG. 4 is a logical flow diagram illustrating one embodiment of ageneralized method for network operation in support ofCPE/FWAout-of-network CPE/FWA according to the present disclosure.

FIG. 4A is a logical flow diagram illustrating one embodiment of amethod of “relaying” data from one or more in-coverage CPE/FWA (e.g.,high-TP or high-throughput CPE/FWA) to a CPE/FWA that is/are completelyout of coverage of a network, according to the present disclosure.

FIGS. 4B and 4C illustrate a logical flow diagram of an exemplaryimplementation of the method of FIG. 4 according to the presentdisclosure, including use of performance monitoring software agents(e.g., iPerf applications).

FIGS. 5A and 5B illustrate a logical flow diagram illustrating anotherembodiment of a method of “relaying” data from one or more in-coverageCPE/FWA (e.g., high-TP or high-throughput CPE/FWA) to a CPE/FWA that iscompletely out of coverage of a wireless network, according to thepresent disclosure.

FIG. 5C is an exemplary table maintained by a network entity (e.g., EPC)for decision making when implementing e.g., the methods of FIGS. 4-5B.

FIG. 6A is a block diagram of a prior art non-roaming referencearchitecture for proximity services (ProSe) according to 3GPP Release14.

FIG. 6B is a block diagram of a prior art inter-PLMN referencearchitecture for proximity services (ProSe) according to 3GPP Release14.

FIG. 6C is a block diagram of a prior art roaming reference architecturefor proximity services (ProSe) according to 3GPP Release 14.

FIG. 7 is a block diagram of illustrating one embodiment of aquasi-licensed wireless network architecture, including ProSe (proximityservices) capability, according to the present disclosure, wherein a3GPP E-UTRAN-based configuration is used.

FIG. 7A is a block diagram of illustrating one embodiment of aquasi-licensed wireless network architecture, including ProSe (proximityservices) capability, according to the present disclosure, wherein a3GPP 5GC-based configuration is used.

FIG. 8 is a logical flow diagram of an exemplary embodiment of ageneralized method for signal flow for D2D connection establishment,according to the present disclosure.

FIG. 8A is a logical flow diagram of an exemplary implementation of themethod of FIG. 8, wherein 3GPP-based D2D protocols are utilized.

FIG. 9 is a ladder diagram illustrating the communication flow forresource allocation to D2D devices by CBSD/xNB (e.g., eNodeB), inaccordance with the methods of FIGS. 4-5B of the present disclosure.

FIG. 10 is a graphical representation of aggregation of multiple SCTPlinks within an exemplary protocol stack of a secondary orout-of-coverage CPE/FWA, according to one embodiment of the presentdisclosure.

FIG. 10A is a logical flow diagram illustrating one embodiment of amethod of aggregating multi-sourced packet data within a secondary orout-of-coverage CPE/FWA, according to the present disclosure.

FIG. 11 is a functional block diagram illustrating the one embodiment ofan exemplary SCTP-based architecture and associated packet flows,according to the present disclosure.

FIG. 12 is a ladder diagram illustrating the communication flow for“relaying” resources from one or more eligible CPE/FWA (e.g., high-TP orhigh-throughput CPE/FWA) within a quasi-licensed band wireless systemwireless network to a CPE/FWA that is completely outside of thequasi-licensed band wireless system, in accordance with the methods ofFIGS. 4-5B.

FIG. 13 is a functional block diagram illustrating one embodiment of anexemplary CPE/FWA apparatus configured for provision of services via theout-of-coverage techniques of the present disclosure.

FIG. 14 is a functional block diagram of an exemplary networkarchitecture useful in conjunction with various principles describedherein, wherein the 3GPP core and ProSe functions are integrated withinone service provider (e.g., MSO) network core.

FIG. 15 is a functional block diagram of an exemplary networkarchitecture useful in conjunction with various principles describedherein, wherein the 3GPP core functions are integrated within a thirdparty service provider (e.g., MNO) network that is in contact with anMSO core.

FIGS. 1-5B and 7-15 ©Copyright 2019 Charter Communications Operating,LLC. All rights reserved.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “access node” refers generally and withoutlimitation to a network node which enables communication between a useror client device and another entity within a network, such as forexample a CBRS CBSD, a cellular xNB, a Wi-Fi AP, or a Wi-Fi-Directenabled client or other device acting as a Group Owner (GO).

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.

As used herein, the term “CBRS” refers without limitation to the CBRSarchitecture and protocols described in Signaling Protocols andProcedures for Citizens Broadband Radio Service (CBRS): Spectrum AccessSystem (SAS)—Citizens Broadband Radio Service Device (CBSD) InterfaceTechnical Specification—Document WINNF-TS-0016, Version V1.2.1.3,January 2018, incorporated herein by reference in its entirety, and anyrelated documents or subsequent versions thereof.

As used herein, the terms “client device” or “user device” or “UE”include, but are not limited to, set-top boxes (e.g., DSTBs), gateways,modems, personal computers (PCs), and minicomputers, whether desktop,laptop, or otherwise, and mobile devices such as handheld computers,PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones,and vehicle infotainment systems or portions thereof.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “D2D” refers generally and without limitationto any mechanism for direct or indirect device-to-device communicationof data, one exemplary instance of which is the 3GPP D2D protocols setforth in e.g., 3GPP Release 14.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0,3.1 and 4.0.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices. Suchprogramming may include literally any information source/receiverincluding, inter alia, free-to-air TV channels, pay TV channels,interactive TV, over-the-top services, streaming services, and theInternet.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants or Releases of the Long-Term Evolutionwireless communication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), and 4G/4.5G LTE.

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM,(G)DDR/2/3/4/5/6 SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g.,NAND/NOR), 3D memory, stacked memory such as HBM/HBM2, and spin Ram,PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “MNO” or “mobile network operator” refer to acellular, satellite phone, WMAN (e.g., 802.16), or other network serviceprovider having infrastructure required to deliver services includingwithout limitation voice and data over those mediums.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications or networking protocols(e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP,3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5G NR, WAP, SIP, UDP, FTP, RTP/RTCP,H.323, etc.).

As used herein, the term “network interface” refers to any signal ordata interface with a component or network including, withoutlimitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g.,USB 2.0, 3.0. OTG), Ethernet (e.g., 10/100, 10/100/1000 (GigabitEthernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radiofrequency tuner (e.g., in-band or OOB, cable modem, etc.),LTE/LTE-A/LTE-U/LTE-LAA, Wi-Fi (802.11), WiMAX (802.16), Z-wave, PAN(e.g., 802.15), or power line carrier (PLC) families.

As used herein the terms “5G” and “New Radio (NR)” refer withoutlimitation to apparatus, methods or systems compliant with 3GPP Release15, and any modifications, subsequent Releases, or amendments orsupplements thereto which are directed to New Radio technology, whetherlicensed or unlicensed.

As used herein, the term “QAM” refers to modulation schemes used forsending signals over e.g., cable or other networks. Such modulationscheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM,256-QAM, etc.) depending on details of a network. A QAM may also referto a physical channel modulated according to the schemes.

As used herein, the term “quasi-licensed” refers without limitation tospectrum which is at least temporarily granted, shared, or allocated foruse on a dynamic or variable basis, whether such spectrum is unlicensed,shared, licensed, or otherwise. Examples of quasi-licensed spectruminclude without limitation CBRS, DSA, GOGEU TVWS (TV White Space), andLSA (Licensed Shared Access) spectrum.

As used herein, the term “SAE (Spectrum Allocation Entity)” referswithout limitation to one or more entities or processes which are taskedwith or function to allocate quasi-licensed spectrum to users. Examplesof SAEs include SAS (CBRS). PMSE management entities, and LSAControllers or Repositories.

As used herein, the term “SAS (Spectrum Access System)” refers withoutlimitation to one or more SAS entities which may be compliant with FCCPart 96 rules and certified for such purpose, including (i) Federal SAS(FSAS), (ii) Commercial SAS (e.g., those operated by private companiesor entities), and (iii) other forms of SAS.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “shared access” refers without limitation to(i) coordinated, licensed sharing such as e.g., traditional fixed linkcoordination in 70/80/90 GHz and the U.S. FCC's current rulemaking onpotential database-coordinated sharing by fixed point-to-multipointdeployments in the C-band (3.7-4.2 GHz); (ii) opportunistic, unlicenseduse of unused spectrum by frequency and location such as TV White Spaceand the U.S. FCC's proposal to authorize unlicensed sharing in theuplink C-band and other bands between 5925 and 7125 MHz; (iii) two-tierLicensed Shared Access (LSA) based on geographic areas and databaseassist such as e.g., within 3GPP LTE band 40 based on multi-year sharingcontracts with tier-one incumbents; and (iv) three-tier shared access(including quasi-licensed uses) such as CBRS.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “users” may include without limitation endusers (e.g., individuals, whether subscribers of the MSO network, theMNO network, or other), the receiving and distribution equipment orinfrastructure such as a CPE/FWA or CBSD, venue operators, third partyservice providers, or even entities within the MSO itself (e.g., aparticular department, system or processing entity).

As used herein, the term “Wi-Fi” refers to, without limitation and asapplicable, any of the variants of IEEE Std. 802.11 or related standardsincluding 802.11a/b/g/n/s/v/ac/ad or 802.11-2012/2013, 802.11-2016, aswell as Wi-Fi Direct (including inter alia, the “Wi-Fi Peer-to-Peer(P2P) Specification”, incorporated herein by reference in its entirety).

As used herein, the term “wireless” means any wireless signal, data,communication, or other interface including without limitation Wi-Fi,Bluetooth/BLE, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CBRS, CDMA (e.g.,IS-95A, WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16),802.20, Zigbee®, Z-wave, narrowband/FDMA, OFDM, PCS/DCS,LTE/LTE-A/LTE-U/LTE-LAA, 5G NR, LoRa, IoT-NB, SigFox, analog cellular,CDPD, satellite systems, millimeter wave or microwave systems, acoustic,and infrared (i.e., IrDA).

As used herein, the term “xNB” refers to any 3GPP-compliant nodeincluding without limitation eNBs (eUTRAN) and gNBs (5G NR).

Overview

In one exemplary aspect, the present disclosure provides methods andapparatus for providing wireless coverage and data rates to at least onecomputerized user device (e.g., fixed wireless access consumer premisesequipment or CPE/FWA) that is outside the coverage area of a wirelessnetwork via relaying network resources through one or more in-coverageCPE/FWA.

In one embodiment, the CPE/FWA are all configured to utilize“quasi-licensed” spectrum provided by the recent CBRS technologyinitiative via 3GPP-based infrastructure and protocols. One or more“in-coverage” CPE/FWA (i.e., those with sufficiently strong signals anddata rates) are used as relays to provide requisite data rates to CPEthat are “out-of-coverage” of a network (or are otherwise prevented fromobtaining or establishing a signal or sufficiently strong signal, suchas via topological obstructions, extended range from a base station, orother such phenomena), and accordingly cannot establish a connection(and accordingly meet any prescribed) user experience or service levelagreement (SLA) requirements. In one variant, the each CPE/FWA haveprocesses operative thereon (e.g., “iPerf” agents) that can measure keyperformance metrics or indicators (KPIs) such as data throughput (TP),latency, jitter, or BER. Participating or eligible CPE/FWA that, e.g.,can sustain data rates higher than required by their own SLAs orrequirements, can act as the relays for other CPE/FWA with no service,such that all the CPE/FWA can meet their performance requirementssimultaneously (or at least are maximized in terms of performancerelative to their prevailing respective SLAs).

In one implementation, the out-of-coverage or “secondary” CPE/FWA cansearch for and acquire in-coverage and/or over-performing CPE/FWA (aka“primary” CPE/FWA), and establish one or more Device-to-Device (D2D)connections to these primary CPE/FWA in order to receive (andsubsequently supplement) signal being received by the secondary CPE viathe primary CPE/FWA, the latter served directly from its/their servingbase station (e.g., 3GPP eNB or gNB operating as a CBRS CBSD). Once theconnection(s) is/are established, the secondary CPE can receive/transmitdata from/to the participating primary CPEs. In one configuration, CBRSGAA and/or PAL spectrum is allocated to the primary and secondaryCPE/FWA (such as by a request to a CBRS SAS) in order to support theadditional D2D connection(s).

In another implementation, packets can be aggregated from multiplein-coverage and/or over-performing CPE via use of Stream ControlTransmission Protocol (SCTP).

The exemplary embodiment described above effectively improves, interalia, coverage area due to the gain and spatial diversity provided viarelaying, without the need to use excessively large power at the servingtransmitter (e.g., gNB/CBSD) and the various issues associatedtherewith. In one sense, the various aspects of the present disclosureallow for a more uniform RF energy distribution within a given region orgeographic area via a type of ad hoc service from one or more primarynodes to one or more secondary nodes (which may vary with time) incontrast with merely increasing radiated power from one (or both) ofcommunicating nodes.

In addition, the provision of enhanced signal quality in both uplink(UL) and downlink (DL) directions for the secondary CPE/FWA via relayingincreases the network capacity without the need to install additionalinfrastructure such as CBSDs and associated backhaul, therebyeffectively adding more customers to the network with a given CAPEX(capital expenditure).

The methods and apparatus described herein may also advantageously beextended to other shared-access architectures (i.e., other than CBRS)such as for example DSA, LSA, and TVWS systems.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedbase station (e.g., 3GPP eNB or gNB) wireless access points usingunlicensed or quasi-licensed spectrum associated with e.g., a managednetwork (e.g., hybrid fiber coax (HFC) cable architecture having amultiple systems operator (MSO), digital networking capability, IPdelivery capability, and a plurality of client devices), or a mobilenetwork operator (MNO), the general principles and advantages of thedisclosure may be extended to other types of radio access technologies(“RATs”), networks and architectures that are configured to deliverdigital data (e.g., text, images, games, software applications, videoand/or audio). Such other networks or architectures may be broadband,narrowband, or otherwise, the following therefore being merely exemplaryin nature.

It will also be appreciated that while described generally in thecontext of a network providing service to a customer or consumer or enduser or subscriber (i.e., within a prescribed venue, or other type ofpremises), the present disclosure may be readily adapted to other typesof environments including, e.g., indoors, outdoors, commercial/retail,or enterprise domain (e.g., businesses), or even governmental uses, suchas those outside the proscribed “incumbent” users such as U.S. DoD andthe like.

Yet other applications are possible.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter alia, InternetProtocol DARPA Internet Program Protocol Specification, IETF RCF 791(September 1981) and Deering et al., Internet Protocol, Version 6 (IPv6)Specification, IETF RFC 2460 (December 1998), each of which isincorporated herein by reference in its entirety), it will beappreciated that the present disclosure may utilize other types ofprotocols (and in fact bearer networks to include other internets andintranets) to implement the described functionality.

Moreover, while the current SAS framework is configured to allocatespectrum in the 3.5 GHz band (specifically 3,550 to 3,700 MHz), it willbe appreciated by those of ordinary skill when provided the presentdisclosure that the methods and apparatus described herein may beconfigured to utilize other “quasi licensed” or other spectrum,including without limitation DSA, LSA, or TVWS systems, and those above4.0 GHz (e.g., currently proposed allocations up to 4.2 GHz, and evenmillimeter wave bands such as those between 24 and 100 GHz).

Additionally, while described primarily in terms of GAA 106 spectrumallocation (see FIG. 1), the methods and apparatus described herein mayalso be adapted for allocation of other “tiers” of CBRS or otherunlicensed spectrum (whether in relation to GAA spectrum, orindependently), including without limitation e.g., so-called PriorityAccess License (PAL) spectrum 104, including selective allocation basedon e.g., role, functionality, resources, availability, subscriptionlevel, geographic/topological considerations, and/or other such factors.

Moreover, while described in the context of quasi-licensed or unlicensedspectrum, it will be appreciated by those of ordinary skill given thepresent disclosure that various of the methods and apparatus describedherein may be applied to reallocation/reassignment of spectrum orbandwidth within a (fully) licensed spectrum context; e.g., for cellularvoice or data bandwidth/spectrum allocation, such as in cases where agiven service provider must alter its current allocation of availablespectrum to users.

Moreover, while some aspects of the present disclosure are described indetail with respect to so-called “4G/4.5G” 3GPP Standards (akaLTE/LTE-A) and so-called 5G “New Radio” (3GPP Release 15 and TS 38.XXXSeries Standards and beyond), such aspects—includingallocation/use/withdrawal of CBRS spectrum—are generally accesstechnology “agnostic” and hence may be used across different accesstechnologies, and can be applied to, inter alia, any type of P2MP(point-to-multipoint) or MP2P (multipoint-to-point) technology,including e.g., Qualcomm Multefire.

It will also be appreciated that while the primary embodiments of themethods and apparatus described herein are cast in terms of provision ofservice to CPE/FWA which are completely out of coverage (i.e., cannotfor all intents and purposes establish any useful connection with anybase station due to e.g., heavy clutter, high levels of interference,topography, etc.), the various aspects of the disclosure may findutility in other types of applications, including e.g., those whereintermittent connectivity can be established, but is unreliable or hasother undesired attributes.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Relaying Architecture—

FIGS. 3A and 3B are block diagrams illustrating an exemplary embodimentof a fixed wireless configuration with relaying functionality utilizingCBRS frequency bands according to the present disclosure. As shown, theconfiguration 300 includes one or more xNB's 301 a, 301 b (e.g., 3GPPeNBs or gNBs), several “in-coverage” premises or houses 302 a, 302 b,and one “out-of-coverage” (OOC) house 302 c. The houses 302 a-c are eachequipped with respective CPE/FWA apparatus 303 a-c, each of the latterincluding CPE devices 311, Wi-Fi or other routers 323, PoE apparatus 325(such as in the architecture of FIG. 2B discussed above), one or moreantenna elements 321, and performance monitoring (e.g., “iPerf” or otherperformance assessment logic or software) agents 317. Each CPE/FWA 303a-c also includes D2D and packet networking functions as describedsubsequently herein (not shown in FIGS. 3A-3B for simplicity).

As discussed in greater detail below, in the exemplary embodiment, theiPerf agent at each house measures (depending on its connection status)key performance indicators (KPIs) such as data throughput (TP), latencyand jitter, which are useful in assessing the needs and capabilities ofeach individual premises. In-coverage, over-performing orhigh-throughput CPE/FWA (such as that 303 a, 303 b respectivelyassociated with Houses 302 a, 302 b in the illustration of FIGS. 3A-3B,by virtue of their location within range of the respective theirrespective serving cells 309 a, 309 b—and also being within a proximityor prescribed range of out-of-coverage CPE/FWA (such as that 303 cassociated with House 302 c)—are accordingly suitable candidates forrelaying their data service to such CPE/FWA 303 c.

It will be appreciated that the use of exemplary performance measurement(e.g., iPerf) processes at the various CPE/FWA devices advantageouslyallows for a very low-overhead and efficient mechanism by which to judgewhether a given primary or serving CPE/FWA is (i) deficient orover-performing in terms of one or more criteria relating to e.g., itsSLA, and/or (ii) can sustain provision of relay or supplementationservices to one or more other (i.e., OOC) CPE/FWA. Specifically, using aperformance-based mechanism such as iPerf in the exemplary embodimentsobviates more sophisticated analyses of channel conditions such as linkbudgets/path loss estimates, channel parameter measurement such as RSSIor RSSQ, determination of PER or BER, etc. Rather, the net or actualperformance of any given link and its associated channel conditions atany given time are readily determined and used as a basis of determiningwhether supplementation is required.

For instance, if served House 1 302 a and House 2 302 b each have an SLA(service level agreement) requirement of 25/3 Mbps (DL/UL), and each ofHouse 1 302 a and House 2 302 b are above the foregoing requirement,having 45/6 Mbps (DL/UL) and 50/8 Mbps (DL/UL), respectively (asdetermined by their respective iPerf clients), while House 3 302 c hasno data throughput (or TP) since it is completely outside the footprintof the serving cells in this example (in a geographic sense), then House1 302 a and/or House 2 302 b can provide data throughput to House 3 302c which is considered to be “out-of-coverage.” Additionally, if afterprovision of such service form House 1, House 3 302 c can only achievesay 75% of its SLA on the DL, and say 90% of its SLA on the UL, then itsperformance is deficient or sub-SLA, and House 2 302 b can be used tosupplement the deficient performance level of House 3 302 c if in factHouse 2 has capacity to spare.

It will be appreciated, however, that SLAs for OOC premises may also beestablished initially at levels known to be supportable by other(primary) CPE, such as based on installation testing, or iPerf analysisof the other CPE in “worst case” conditions. For instance, if it isknown that a maximum theoretical SLA for the OOC CPE is (based onworst-case scenarios for all eligible primary CPE) is X Mbps in UL and YMbps in DL, then the SLA for that OOC CPE may purposely not beestablished above those values, thereby avoiding customer disappointmentor frustration. If subsequently additional capacity becomes available,then the OOC device can be given “upgrades” on its SLA, whetherexplicitly by contract, or implicitly via added capacity when availableeven with no formal commitment by the MSO to do so.

FIG. 3B illustrates the fixed wireless configuration with relayingfunctionality utilizing CBRS frequency bands of the type utilized inFIG. 3A, further showing the constituent components of each CPE/FWA 303according to one embodiment of the present disclosure. As shown (andsubsequently described in greater detail herein), each CPE/FWA 303includes a performance monitoring client which enables in effectstand-alone assessment of its own performance relative to its particularSLA (which may not be the same for each of the CPE/houses shown,depending on contractual agreements, physical limitation of theinstallation, etc.). As such, each CPE/FWA in this embodiment can bothassess itself relative to its own SLA, and “advertise itself” (whetheractively, such as via request or advertisement messaging) as eitherneeding a certain amount of network resources from primary CPE/FWA localto it, or being able to provide a certain amount of network resources toout-of-coverage or secondary CPE/FWA devices.

As previously noted, one primary attribute of the disclosure relates toits ability to provide coverage and data rates to CPE/FWA that arecompletely outside the coverage area of a network. Specifically, toreceive signal power at the “out-of-coverage” coverage CPE/FWA (andthereby establish and/or enhance its data rate), the CPE/FWA may receivethe signal from multiple in-coverage or relaying CPE/FWA. It will beappreciated that depending on the type of antenna elements 321 used ineach CPE/FWA (e.g., directional or omni-directional), even a high-TPCPE/FWA 303 a, 303 b (FIG. 3A) may not be able to supply or supplementan out-of-coverage CPE/FWA 303 c if the antenna geometry of thereceiving devices does not support it, such as where highly directionalantenna elements are utilized on one or both CPE/FWA and they arealigned to their serving xNB versus the other CPE/FWA.

Hence, in one implementation, the CPE/FWA may also have “smart” antennacapability that can steer the radiation pattern (e.g., lobes) toward thedesired target CPE/FWA or serving base station 301 to maximize e.g., thereceived SINR. This steering may be accomplished via mechanical means(e.g., actually moving the antenna element or array in azimuth and/orelevation/tilt), and/or electronic steering means such as beamforming(e.g., as may be used in LTE) or so-called “massive MIMO” in 5G NRtechnology).

In one such implementation, a directional or steerable device such asthe BLiNQ SC-300S dynamic device manufactured by BLiNQ NetworksCorporation is used, which includes software-enabled targeting ofspecific areas to enable efficient coverage.

In another such implementation, each CPE/FWA employing multipledirectional antenna element technology measures the received signal fromits associated base station or another CPE/FWA in communicationtherewith (e.g., via D2D mechanisms such as ProSe described subsequentlyherein), and extracts multipath wireless channel information relating tophase and amplitude from the received signal. Such information is usedto combine the output of the multiple antennas in such a way as to forma narrow sectorized beam towards the target base station or anotherCPE/FWA as appropriate, including as input to any mechanical steeringmechanism (e.g., to change azimuth of the element/array). Various othersimilar approaches for optimizing SINR or other signal-strength relatedparameters will be recognized by those of ordinary skill when given thepresent disclosure.

Methodology—

Various methods and embodiments thereof for providing throughput andcoverage utilizing relaying via quasi-licensed (e.g., CBRS GAA or PAL)spectrum according to the present disclosure are now described withrespect to FIGS. 4-5B.

FIG. 4 illustrates one embodiment of a generalized method for networkoperation in support of providing services to out-of-coverage CPE/FWAaccording to the disclosure. As shown, the method 400 includes firstforming one or more associations between an out-of-coverage CPE/FWA 302c and one or more in-coverage CPE/FWA 302 a, 302 b per step 402. Asdiscussed in greater detail below, such associations may be for exampleat the instigation of the out-of-coverage CPE/FWA 302 c, or thein-coverage CPE/FWA, or even a network entity such as the EPC or 5GC orother.

Next, per step 404, the network allocates resources among the variousparticipating CPE/FWA. In one such embodiment, the EPC or 5GC is taskedwith generating resource allocations (including how much capacity orresources a primary or in-coverage CPE/FWA can provide to any associatedout-of-coverage CPE/FWA which it will be prospectively serving.

Per step 406, after the resource allocation is complete, theparticipating CPE are registered with e.g., the SAS according to theirrespective roles (including for instance the primary CPE as a CBSD, andthe secondary CPE as an FWA for utilization of e.g., GAA spectrum tocommunicate with the primary CPE/CBSD via one or more establishedcommunication channels).

Per step 408, the primary and secondary CPE are operated based on theirregistered roles and spectrum grants, utilizing the establishedchannels.

FIG. 4A shows one exemplary embodiment of the method used by adecision-making network entity (e.g., EPC or 5GC or other networkentity) in providing network resources to an “out-of-coverage” orsecondary CPE/FWA via one or more in-coverage or “primary” CPE FWA,according to the present disclosure.

As shown, the method 410 includes first identifying a secondary CPE/FWAthat is not connected to any backhaul (e.g., has no connection to an xNB301 a, 302 b) (step 411).

In one embodiment, the identification of the secondary or OOC CPE/FWAincludes synchronization with, and discovery of, the secondary CPE/FWAvia D2D mechanisms such as ProSe described subsequently herein. Asdescribed elsewhere herein, in one approach, a D2D communication channelis established between the various requesting/responding CPE/FWAs so asto facilitate establishment of the ultimate D2D “relay” channel (e.g., achannel via the primary air interfaces of the device using CBRSSAS-allocated bandwidth). Broadly speaking, a primary or secondaryCPE/FWA according to the present disclosure may implement any number ofprotocols (the 3GPP D2D discovery protocols being just one example) toidentify nearby or local CPE/FWA with which data connections may beestablished. As such, the present disclosure contemplates variousembodiments wherein: (i) the out-of-coverage or secondary CPE initiatesdiscovery of other CPE (via e.g., open announcement or request/responseprotocols described subsequently herein, or other types of “probe”communications); (ii) the primary CPE advertises itself via prescribedmethods (D2D announcements, beacons, or other methods), and (iii) wherethe discovery of the primary and secondary CPE of each other, eitherbilaterally or unilaterally, is managed or invoked by a network entity,such as where a primary CPE is instigated by the xNB with which itconnected to announce itself to local secondary CPE.

It will also be appreciated that in certain configurations, thesecondary CPE may be a new installation (i.e., it has never previouslyformed any association or connection with any xNB or other CPE/FWA), andhence is in effect completely ignorant to its surroundings. In suchcases, the newly installed CPE/FWA can be configured to invoke a“learning” algorithm (such as via 3GPP D2D protocols described ingreater detail below) whereby it discovers and characterizes itssurroundings before any D2D communication channel is established. Thisprotocol may also include relay by one or more of the primary CPE whichit discovers of data regarding the new CPE to the xNB (and ultimatelyEPC/5GC) serving the primary CPE so that the network can becomecognizant of the new CPE before it is subject to resource allocation,registration, and other procedures pursuant to providing it “out ofcoverage” broadband service.

Returning to FIG. 4A per step 412, performance data is obtained usingthe performance monitoring process (e.g., iPerf 317) operative toexecute on each CPE/FWA 303. Initially, the secondary CPE/FWA will haveno service, and therefore only the performance of one or more primary orin-coverage CPE/FWA are monitored to identify one or more candidate(e.g., geographically local) CPE/FWA 303 a, 303 b which can putativelyprovide some bandwidth to the secondary CPE/FWA 303 c, per step 414.

For instance, the measured or actual data rate over a prescribed periodof time (e.g., averaged over n minutes) for UL and/or DL is assessed,and compared to the relevant SLA(s). When the prescribed criterion isexceeded for particular CPE/FWA, those primary CPE/FWA can spare some oftheir bandwidth for the secondary CPE/FWA 303 c.

Besides monitoring performance and identifying particular primaryCPE/FWA to use as “relays” to the secondary CPE/FWA 303 c, steps 412 and414 may also include calculating how much bandwidth the primaryCPE/FWA(s) can provide to the secondary CPE/FWA 303 c while still themaintaining adequate performance of its backhaul and meeting orexceeding the requisite parameters indicated by the relevant SLA(s).

Additionally, once the secondary CPE/FWA 303 c ultimately establishesdata service and receives bandwidth from say one primary CPE/FWA 303 a,steps 412 and 414 can include calculating how much bandwidth thesecondary CPE/FWA 303 c will need from another primary CPE/FWA 303 b tomeet one or more parameters, such as those required by the SLA of thesecondary CPE. It is further contemplated that in cases where theresimply is not enough bandwidth or capacity available to the secondaryCPE to meet its SLA (due to e.g., only one available candidate primaryCPE which does not have sufficient capacity to meet the secondary CPESLA as well as its own), allocation algorithms may be used to “fairly”(or unfairly) allocate the division of available resources between thetwo CPE, or alternative mechanisms may be used to try to obtainadditional capacity (such as e.g., requesting a switch to PAL spectrumfrom GAA, since PAL is presumptively less “crowded” and hence has lessinterference and ostensibly better channel characteristics which may beable to support higher data rates).

At step 415, the identified one or more primary CPE/FWA 303 a, 303 breceive a communication indicating a grant of spectrum/resources (whichmay include instructions for providing the granted spectrum/resources tothe secondary CPE/FWA 303 c). In various embodiments, the receipt of thecommunication by the identified one or more CPE/FWA 303 a, 303 b can bebased on one or more requests initiated from the identified one or moreCPE/FWA 303 a, 303 b, and/or from the secondary CPE/FWA 303 c via theidentified one or more CPE/FWA 303 a, 303 b.

For example, in one variant, the secondary CPE/FWA 303 c transmitsdirectly (or via proxy process) a communication to the identified one ormore CPE/FWA 303 a, 303 b requesting resources, after discovery thereof.Based on the request received from the secondary CPE/FWA 303 c, the oneor more primary CPE/FWA 303 a, 303 b then transmit a request to therelevant entity or entities responsible for granting spectrum (e.g., tothe cognizant SAS via the serving xNB and core and DP).

After any requests have been received and spectrum is granted, theprimary CPE/FWA 303 a, 303 b provides the secondary CPE/FWA 303 c withthe granted resources (e.g., via the established D2D side channels) perstep 417, and per step 419, the performance of the secondary CPE/FWA 303c is monitored to determine whether the necessary SLA goals or criterionare met, or whether supplementation is needed.

For example, although at this point the secondary CPE/FWA 303 c has beengranted at least some resources, the date rates from the identifiedprimary CPE/FWA initially used to relay network resources may not beenough to meet the necessary SLA goals or criterion, as determined bye.g., the iPerf client 317 operative to execute on the secondary CPE.Accordingly, method 410 then reiterates the process again starting atsteps 412 and 414 to identify other candidate primary CPE/FWA that cansupplement the throughput of the secondary CPE/FWA 303 c.

Referring now to FIGS. 4B and 4C, one embodiment of a methodology 420 ofoperating a wireless network is shown and described, in the exemplarycontext of a CBRS-based system with SAS, CBSD/xNBs and EPC/5GC, andin-coverage and out-of-coverage CPE/FWA devices.

Per step 421 of the method 420, each primary CPE/FWA utilizes itsindigenous iPerf agent to measure KPIs (key performance indicators) suchas data throughput (TP), latency, and jitter. The measurement by theCPE/FWA can be e.g., constant or periodic (e.g., according to aprescribed schedule), or alternatively event-based, such as based on asignal sent from a decision-making entity (e.g., SAS, CBSD/xNBs orEPC/5GC).

Next, per step 423, measured data from step 421 is compared withrespective SLAs of the CPE/FWA, and if their data rates are higher thanthe respective SLA (or other relative criterion as discussed elsewhereherein), those the CPE/FWA can act as relays or supplementation devicesfor other CPE, such as those out-of-network. In one embodiment, thecomparison may be conducted at the primary CPE/FWA. The results (e.g.,how much the bandwidth the CPE/FWA can spare) can then be sent upstreamin the form of a request to a network resource-granting entity (e.g.,EPC or 5GC). In another embodiment, the comparison may be conducted atthe decision-making entity. In this embodiment, the CPE/FWA would sendthe raw or pre-processed measured data to the relevant decision-makingentity for processing thereat. In some embodiments, some network entitymay maintain a database or data structure (e.g., such as the exemplarydata structure of FIG. 5C discussed infra) for decision-making andtracking of network resource allocations.

Next per step 425, any out-of-coverage CPE/FWAs areidentified/discovered. Since out-of-coverage CPE/FWA 303 c is out ofnetwork and unable to synchronize itself to any serving xNB, it must doso through the in-coverage CPE/FWA 303 a, 303 b. For instance, in oneapproach, the out-of-coverage CPE/FWA 303 c cannot advertise itself tothe “network” since it is out of the coverage area thereof, so it mustdirectly contact other CPE/FWA 303 a, 303 b within the network, via D2Dside channel or other mechanism. The out-of-coverage CPE/FWA 303 c canadvertise itself to the CPE/FWA 303 a, 303 b using established protocolssuch as those relating to 3GPP D2D discovery.

Next, per step 427, the out-of-coverage CPE 303 c (or their proxyprocess) identify one or more eligible in-coverage CPE (e.g., CPE/FWAwhich are within range and which are available to engage in D2Ddiscovery and communication protocols as described in detailsubsequently herein), and establish a D2D connection to the in-coverageCPEs at step 429 so as to support communications pursuant toauthentication, IP address discovery, spectrum requests, determinationof throughput capability of the serving CPE/FWA 303 a, 303 b, spectrumgrant communication, etc.).

It will be appreciated that while the aforementioned process envisionsthe capability of the secondary CPE to establish D2D communicationsbased purely on non-TP performance related criteria (i.e., which CPE areeligible for D2D per 3GPP protocols and which display suitable channelcharacteristics), the present disclosure contemplates configurationswherein the iPerf data measured by a primary CPE is passed to thesecondary CPE as part of the D2D discovery or communicationestablishment procedure, in effect giving the secondary CPE a “preview”as to each prospective primary CPE's capability in terms of ultimateresource allocations. For example, in one such configuration, anannouncing primary CPE includes payload data relating to available iPerfthroughput which the secondary CPE can utilize to determine whether itwishes to establish full D2D communications with that CPE (e.g., toassist in ranking candidate primary CPE by the secondary CPE).

In another configuration, the secondary CPE obtains previews fromvarious primary CPEs. In one such variant, the performance monitor(e.g., iPerf) process on each of the candidate primary CPEs measure andreport performance to the network (e.g., EPC or 5GC). A decision processwithin the core network is then utilized to, based on the providedperformance data, generate a connection plan, including directing one ormore candidate primary CPEs to provide data service to the secondaryCPE. The secondary CPE utilizes its own performance assessment after theaforementioned connection(s) is/are established to measure datathroughput. These measurements are then reported back to the corenetwork decision process, wherein the initial connection plan may bemaintained or adjusted based on the actual performance experienced bythe secondary CPE (e.g., relative to its required SLA levels). In thisfashion, the core network process maintains cognizance over the variousprimary CPE (and served secondary CPE) in order to enable more efficientnetwork configuration as a whole (e.g., to avoid overloading certainprimary CPE, avoid creation of undue levels of interference between agiven primary CPE and secondary CPE, and/or achieve other aims such asoptimizing maximal throughput across a number of different CPE within agiven area).

Next per step 431, resource requirements for the out-of-coverage CPE/FWAdevice(s) are determined for the relaying in-coverage CPE/FWA. In oneembodiment, initially, use of the iPerf agent on the out-of-coverageCPE/FWA device may be obviated since the out-of-coverage CPE/FWA devicehas no service at all, and therefore will simply need the resourcesrequired by its SLA. However, once the out-of-coverage CPE/FWA devicereceives some resources from another CPE/FWA device, the iPerf agent onthe out-of-coverage CPE/FWA device may be used to determine how muchadditional resources are required from other CPE/FWA to meet the target(e.g., SLA). Note that the iPerf of the secondary CPE may also send theraw iPerf data to another entity (including a primary CPE and/or theEPC/5GC) for such determination.

As a brief aside, the exemplary iPerf client used in the variousembodiments described herein is a tool for network performancemeasurement and tuning that can produce standardized performancemeasurements. iPerf can be configured with client and serverfunctionality, and can create its own data streams to measure thethroughput between the two “ends” of the connection in one or bothdirections. The data streams can be for example Transmission ControlProtocol (TCP) or User Datagram Protocol (UDP), and various parametersare user configurable (in the present context, by MSO design or testingpersonnel, or even dynamically via remote control from a networkprocess). IPerf is typically embodied as open-source software written inC, and runs on various platforms including Linux and Windows.Notwithstanding, the present disclosure contemplates use of otherperformance monitoring techniques (whether implemented by the DUT(device under test) such as the CPE/FWA “self-assessing” itself, or fromthe other end of the connection, such as by a serving xNB 301 or primaryCPE/FWA).

At step 433, the in-coverage CPE 303 a, 303 b calculate the amount ofresources that can be allocated to the out-of-coverage CPE 303 c (e.g.,using their own iPerf client processes and respective SLAs). Note thatin one embodiment, to avoid repeated request/grant/withdrawal cyclesbetween two CPE/FWAs (i.e., “dither”), the iPerfs and monitoringalgorithms can be configured to smooth (e.g., average) out the variousparameters over time, and also anticipate changes in operatingconditions or demand which may occur for the serving (or served)CPE/FWA, or implement a hysteresis function which mitigates such dither.For instance, if a given serving CPE/FWA 303 a, 303 b historically islargely inactive between 2:00 AM and 5:00 AM local time, it can besafely presumed in most cases that any excess capacity over and aboveSLA will be stable and not subject to sudden retraction or withdrawal bythe serving CPE/FWA, such as might be caused by a user streamingmultiple videos as might occur during normal (waking) hours.

Similarly, if a requesting CPE 303 c has already received bandwidth froman in-coverage CPE, and therefore only transiently falls below one ormore of its SLA criteria, the algorithms may be configured to ignoresuch transients, and only allow for supplementation requests that aremore pervasive and continuous in nature. Likewise, if the requestingCPE/FWA 303 c is configured to anticipate that, even though performanceis deficient or below requisite levels, that no salient demand will beforthcoming for say several hours (e.g., during the same late-nightwindow as referenced above), it may selectively forestall issuingrequests or advertisements for resources, since the lack of performanceis a logical “don't care” state, and the supplementation would not beused anyway even if provided.

Next per step 435, the in-coverage CPE 303 a, 303 b register to the SASas CBSDs and request spectrum grants.

Per step 437, the in-coverage CPE 303 a, 303 b receive the grant fromthe SAS, and per step 439, a data session between the requesting orsecondary CPE/FWA 303 c and the serving or primary CPE/FWA 303 a, 303 bis established using the granted spectrum. In one embodiment, 3GPP sidechannel discovery and establishment procedures (including RACH,establishment of RRC Connected State, etc.) are performed.

Next per step 441, the requesting (secondary) CPE/FWA 303 c requestsdata service from the in-coverage CPE 303 a, 303 b via normal 3GPPsignaling, and data exchange between the various CPE/FWAs (served andserving) occurs to support service flows for the requesting CPE/FWA 303c per step 443.

Per step 445, the data service support starts between the CPE to providethe requested resources. The data exchange process between the serving(primary) and served (secondary) CPE is dynamic, and if the resourcesare not needed anymore, the SAS grant is relinquished by the servingCPE/FWA (e.g., via communication to the SAS) per step 447, and D2Dconnection between the primary and secondary CPE/FWAs is terminated.

FIGS. 5A and 5B illustrate an embodiment of a method of operation usedby an in-coverage CPE/FWA in providing network resources according tothe present disclosure.

As shown, the method 500 includes the serving or in-coverage CPE/FWA 303a, 303 b receiving a request for resources from a requesting orout-of-coverage CPE/FWA 303 c as described elsewhere herein (whether viaLTE D2D synchronization, polling/pull, active request “push” by theout-of-coverage CPE/FWA, from an EPC/5GC, via a proxy process, or other)per step 502. Step 502 may also include detecting an announcement oradvertisement message, beacon, probe, or the like from theout-of-coverage CPE/FWA 303 c for initial synchronization and discovery.

Per step 504, the receiving CPE/FWA evaluates its own backhaulperformance relative to its SLA. In one embodiment, the receivingCPE/FWA 303 c is completely outside the coverage area of the backhauland therefore would need the entire service level required by its SLA.

Per step 506, based on the evaluation of step 504, the CPE/FWA or aproxy (e.g., the 5GC or EPC) identifies an amount of resources which itcan provide, and compares this amount to the requested or requisiteamount associated with the request (step 508). In one approach, if theavailable capacity is adequate to support the request (step 510), thenthe primary CPE/FWA 303 a, 303 b notifies the requesting CPE/FWA 303 cof the available resources (e.g., via D2D “side channel” messaging) perstep 512.

At step 514, the serving CPE/FWA obtains a spectrum grant viaregistration of itself as a CBSD, and the secondary CPE/FWA as an FWA,with the SAS, and establishes the channel with the requesting CPE/FWA303 c as previously described (step 516). The relaying CPE then providesthe amount of data services to the requesting CPE using the grantedspectrum per step 518.

It is noted that the foregoing logic may be modified in a number ofways, depending on the particular application and desired functionality.For instance, in one variant, the secondary CPE is not apprised of anyavailability of spectrum or services from the primary CPE until thelatter registers itself and the secondary CPE with the SAS, and obtainsthe spectrum grant.

In another variant, even when the entirety requested or required amountof capacity is not available from the primary CPE/FWA, the request isnot refused, and the primary CPE allocates (e.g., at direction of theEPC or 5GC) what it has in terms of available capacity to the secondaryCPE; that is, the decision to service the secondary CPE is not “binary”with respect to the requested capacity.

In yet other variants, the network is configured such that the EPC/5GCand primary CPE always allocates what excess the primary CPE hasirrespective of any explicit data in a request (e.g., in cases where thesecondary CPE does not provide or is incapable of providing an estimateof its required capacity), effectively akin to an “any service is betterthan none” paradigm.

It will also be appreciated that while a single served CPE/FWA 303 c isdescribed in the context of the foregoing discussion, a given servingCPE/FWA 303 a, 303 b may in fact service multiple requestingout-of-coverage CPE/FWA simultaneously. For example, a given primary orserving CPE/FWA may receive a request for resources from a firstsecondary CPE/FWA, and provide service to that device, and thensubsequently receive a request from another “out-of-coverage” CPE/FWA,and assuming that its performance/capability are adequate, supplementthat device as well. In one such approach, the two requesting CPE areserved via two different spectrum grants (i.e., using two differentcarriers or bands, or even types of spectrum such as GAA for one CPE inone sector, and PAL for another CPE in another sector, the latter havinga higher interference level in the GAA frequency band), and one or moreallocated direction antenna elements and corresponding formed beams (thetwo requesting CPE presumed to be disparate enough in azimuth orelevation such that simultaneous supplementation is possible withoutunacceptable levels of interference).

In another approach, a time-share or TDM based scheme is used on thesame carrier or set of sub-bands. Using OFDM-based 3GPP mechanisms,different time/frequency resource blocks are allocated to each servedCPE/FWA as well. Each CPE may also be fitted with two or more separatetransceiver chains (front ends) and associated baseband processing suchthat each served CPE may have its own dedicated air interface with aserving CPE/FWA if desired. Numerous other approaches to simultaneousprovision of service to two or more requesting or secondary CPE/FWA willbe recognized by those of ordinary skill when given the presentdisclosure.

Conversely, as previously noted, the present disclosure alsocontemplates provision of capacity or services by two or more primaryCPE to a single recipient secondary CPE, such as e.g., where each of thetwo or more primary CPE are required to meet the SLA requirements of thesecondary CPE/FWA.

Exemplary Data Structure Maintained for Decision-Making—

FIG. 5C shows an exemplary table maintained by a network entity (e.g.,EPC or 5GC) for decision making (e.g., pursuant to the methodologies ofFIGS. 4-5B), according to the present disclosure.

As described elsewhere herein, each primary CPE/FWA in one embodimentutilizes its indigenous iPerf agent to measure KPIs (key performanceindicators) such as TP, latency, and jitter.

These measurements can be sent to the relevant decision-making entity(e.g., EPC or 5GC or other network controller) and maintained in adatabase or data structure (e.g., table) for decision-making.

In the exemplary table of FIG. 5c , the data includes: (i)identification of each primary and secondary CPE/FWA, (ii) the status(active, inactive) of each primary and secondary CPE/FWA, (iii) therespective SLAs or other parameters of each primary and secondaryCPE/FWA, and (iv) the channel conditions and network KPIs for eachconnection between the primary and secondary CPE/FWAs. As will beappreciated, the data structure of FIG. 5C is a high-levelrepresentation of types of data which may be maintained by the network;in some implementations, such data may be part of IE's (informationelements) such as those used pursuant to 3GPP protocols, with certainfields of the table of FIG. 5C gleaned from one or more extant IEs usedduring e.g., channel establishment, connection, etc. For instance,channel conditions for a D2D link may be monitored or gauged viaexisting 3GPP-based measurements taken for channel sounding, signalstrength, BER/PER, etc. The data link performance measurements, whileenvisaged as being derived from iPerf client measurements on eachCPE/FWA, may also be supplemented or obtained from other sources inalternate embodiments.

It is also understood that other data can be maintained concurrent orassociated with that of FIG. 5C, such as that related to QoS or otherpolicies or rules (e.g., those prescribed by the MSO for certaincustomers or tiers of service), germane topographical features orconditions, propagation or connection paths, other operating conditionssuch as network status, etc. This information helps in selectivelyestablishing or terminating suitable D2D links for out-of-coverageCPE/FWA service provision.

Device to Device (D2D) Communication Mechanisms—

As previously referenced, certain embodiments of the apparatus andmethods of the present disclosure establish communication between thevarious CPE/FWA devices 303 within a given network area using 3GPP-basedProximity Services (ProSe). This capability allows for, inter alia, theprovision of data relating to a number of parameters to the CPEs toenable relay/service connectivity among themselves, assignment of uniqueIDs to each of the CPE, and establishment/teardown of communicationchannels between the various participating CPE/FWA. In some embodiments,these parameters include for instance: (i) security parameters (e.g.,relating to mutual authentication, exchange of session or other keys, orother); (ii) group membership data and unicast/multicast addresses(e.g., IP addresses by which P-GW or other such entities within thenetwork can address traffic), (iii) radio resource and relatedparameters; and (iv) service request/response messaging. It will beappreciated however that while the exemplary embodiments describedherein are cast in terms of 3GPP ProSe and associated D2D mechanisms,the disclosure is in no way so limited, and in fact those of ordinaryskill will recognize comparable implementations given the presentdisclosure.

As a brief aside, 3GPP TS 32.277 V14.0.0 (2016-09), “TechnicalSpecification—3rd Generation Partnership Project; TechnicalSpecification Group Services and System Aspects; Telecommunicationmanagement; Charging management; Proximity-based Services (ProSe)charging (Release 14),” which is incorporated herein by reference,describes the exemplary ProSe functionality utilized in some embodimentsof the present disclosure. First introduced in Release 12 of the 3GPPspecifications, ProSe (Proximity Services) is a D2D (Device-to-Device)technology that allows 3GPP-compliant devices to detect on other, and tocommunicate directly as opposed to via the core functions. It uses newfunctional elements including a “sidelink” air interface for directconnectivity between devices. In comparison to existing D2D andproximity networking technologies, ProSe offers some benefits such asenhanced scalability and management, privacy, security and mobile devicebattery-efficiency.

FIG. 6A illustrates one prior art non-roaming reference architecture forthe above-described proximity services (ProSe) according to 3GPP Release14.

FIG. 6B is a block diagram of a prior art inter-PLMN referencearchitecture for proximity services (ProSe) according to 3GPP Release14.

FIG. 6C is a block diagram of a prior art roaming reference architecturefor proximity services (ProSe) according to 3GPP Release 14.

As can be seen in each of the above Release 14 architectures, aclient-server model is used wherein a ProSe application on a UEcommunicates logically with a ProSe application server via e.g., a ProSenetwork function within the PLMN (public land mobile network) associatedwith the UE. A PC5 inter-UE communication interface is utilized for D2Dcommunication (i.e., UE to UE) as shown, and Uu interfaces are used fromthe UEs back to the E-UTRAN.

3GPP D2D functionality was designed to operate regardless of theoperational status of a given UE. Accordingly, three (3) scenarios wereidentified by 3GPP for D2D operation: (i) in-coverage, (ii) partialcoverage, and (iii) out-of-coverage (which are not necessarily the sameas CPE/FWA in-coverage or out-of-coverage designations or definitions asapplied to the MSO architecture of FIGS. 3A and 3B as previouslydiscussed). When the UE is in-coverage (3GPP definition), the D2Dfunctions are network assisted; for example, the UE use theconfiguration and control information provided by the network via theeNB, as well as preconfigured parameters of the UE itself. When the UEis out-of-coverage, it utilizes the preconfigured parameters only,thereby enabling autonomous operations. Partial coverage (basically ahybrid of (i) and (iii) under 3GPP standards) allows UEs within networkcoverage to provide at least some system information to out-of-coverageUEs.

D2D communication over a 3GPP sidelink is performed using periodicallyrepeating temporal periods. Two spaced channels are used; the PhysicalSidelink Control Channel (PSCCH) and the Physical Sidelink SharedChannel (PSSCH). Each channel is provided a resource pool comprised ofprescribed Resource Blocks (RBs) in the frequency domain, and subframesin the time domain.

The control channel (PSCCH) is used by ProSe-enabled UEs to send asidelink control information (SCI) message. This message includes avariety of data, such as addressed recipient, transmission informationsuch as the group destination ID, the modulation and coding scheme(MCS), and the PSSCH resource assignment in time and frequency, as wellas other data. The SCI message allows the target UE(s) to tune to thecorresponding resources in the PSSCH.

A given UE may be associated with one or more group IDs, and accessesthe control channel time duration to determine if another UE is going totransmit something addressed to the group of which the monitoring UE isa member.

Two resource allocation (RA) modes are available in D2D communications(contrast: discovery); i.e., Mode 1 and Mode 2. In-coverage UEs canoperate in either Mode; however, out-of-coverage UEs may operate only inMode 2. In RA Mode 1, various functions are performed by or assisted bythe eNB, such as resource scheduling. In Mode 2, a given UE managesaspects of its own resource scheduling autonomously, relying for exampleon preconfigured settings within the UE itself. For example, PSCCH andPSSCH resources can be selected at random from their respective resourcepools by the UE autonomously in RA Mode 2. For Mode 1, the UE needs tobe in the RRC_CONNECTED state, whereas for Mode 2, UEs in RRC IDLE state(or even out-of-coverage) can utilize the protocol.

D2D discovery (contrast: communication as described above) is afunctionality that allows the detection of services and applicationsoffered by other UEs in physical proximity to a given UE. Discoveryoperates effectively independent from direct communication, and neitheris required to precede the other. D2D discovery protocols allow UEswhich have elected to be discovery-enabled to be directly identified byother discovery-enabled UEs.

Two models of discovery are used: (i) Model A is based on an openannouncement procedure, where a given UE broadcasts information to otherprospective discovery-enabled UE(s); (ii) Model B uses arequest/response protocol whereby a UE may request prescribedinformation from other UE(s). In addition to the discovery modesdiscussed above, two discovery resource allocation types are defined by3GPP: Type 1 and Type 2B. In Type 1, (i.e., “UE-Selected”), a UEindependently and arbitrarily selects the discovery resources fortransmission of discovery messages. In Type 2B (i.e., “Scheduled”) aUE-dedicated resource allocation is provided by the eNodeB for use bythe UE.

For both resource allocation types, one salient objective is to mitigatethe assignment of common time/frequency resources to different discoverytransmissions. In the “Scheduled” type (Type 2B), conflicts areprevented, since the eNB is fully responsible for the allocationdecisions. If the UEs are in-coverage, their “SyncRef” (synchronizationreference) is provided by the eNodeB, and the synchronizationconfiguration can be extracted from the SIB18 and SIB19 messages.

For the “UE-selected” resource allocation type (Type 1), UEs selectautonomously the exact time and frequency resources from their availablepool using a randomization pattern based on a MAC configurationparameter, from which the actual subframe and PRB indexes (within thepool) for carrying the discovery message are extracted. Different UEsideally select different resources to avoid interference. At thereceiver side, a UE can monitor for such transmissions using a number ofdifferent approaches, such as by monitoring resources corresponding todifferent configuration parameter settings which might have beenutilized by the transmitting UE.

The 3GPP standards also define Sidelink synchronization informationtransmission procedures, including when a UE should act as a SyncRef,and distribute synchronization information. When in-coverage, the UE isdesignated as a SyncRef if the eNodeB explicitly instructs it to be, aswell as when the eNodeB signal strength is below a prescribed threshold.An out-of-coverage UE assumes a SyncRef role if it is transmitting inthe Sidelink and either (i) is not in possession of a selected SyncRef,or (ii) the signal strength of its selected SyncRef is below aprescribed threshold. When the UE assumes the role as a SyncRef, itperiodically transmits Sidelink Synchronization Signals (SLSS)announcing its synchronization information. An SLSS is composed of fourelements: (i) The Primary Sidelink Synchronization Signal (PSSS), (ii)the Secondary Sidelink Synchronization Signal (SSSS), (iii) theDemodulation Reference Signals (DMRS), and (iv) the Physical SidelinkBroadcast Channel (PSBCH). The PSSS and SSSS are used for time andfrequency reference, collectively defining the SyncRef SLSS identifier(SLSSID). A subset of SLSSIDs is used for identifying SyncRefsin-coverage, and another subset used for out-of-coverage identification.

The PSBCH contains system level information used for configuration of asynchronizing (receiving) UE. The DMRS is used as a reference for CE(channel estimation), demodulation of the PSBCH, and measurement ofSidelink Reference Signal Received Power (S-RSRP) in the recipient UE.

The UEs search for available SyncRefs, measure the S-RSRP of thedetected ones if any, and synchronize to the “best” one according to aSidelink synchronization reference protocol.

With the foregoing as a backdrop, embodiments of the present disclosure(see e.g., FIG. 7) leverage the ProSe architecture to enable, amongother things, CPE/FWA-to-CPE/FWA communication in support of coverage ofsecondary CPE/FWA. In the architecture 700 of FIG. 7, theout-of-coverage CPE 303 c (i.e., those which for instance do not meetMSO specified performance levels such as SLA requirements, as opposed tounderlying technology definitions of “out of coverage” such as thosedescribed above with respect to the exemplary 3GPP protocols, the formerwhich may be based in part on the latter, or wholly independenttherefrom), receive/transmit from/to the E-UTRAN (including eNBs 301)over the Uu interface. Also, the serving (aka “primary” or high-TP) CPEs303 a, 303 b receive/transmit data from/to the out-of-coverage CPE 303 cover the PC5 interface. This data is aggregated in the exemplaryembodiment at the transport layer as subsequently described herein withrespect to FIGS. 10, 10A and 10B.

In the illustrated embodiment, the Evolved Packet Core (EPC) 703 or 5GC(depending on configuration) transfers the aggregated data packet fromeNBs to e.g., the Internet 715. The EPC unit includes a MobilityManagement Entity (MMS) 711, Packet Data Gateway (P-GW) 70, EvolvedPacket Data Gateway (E-PDG), Serving Gateway (S-GW) 712, Policy andCharging Rules Function (PCFR), and Home Subscriber Server (HSS) 707.The ProSe application server 705 communicates directly with the EPC core703 via the PC2 interface (or alternatively may be communicative withthe EPC via the Internet 715) to provide support of the ProSe “apps”operative on each CPE/FWA within the architecture, including via theillustrated PC1 interface 713.

FIG. 7A shows another embodiment of the ProSe architecture 730 of thepresent disclosure, wherein 5G NR network entities are utilized(including gNBs 301 and NG-RAN, 5GC 733, PCF 739, UDM/HSS 737, and AMF711), as well as the ProSe app to Server interface 743.

As will be recognized, one major difference between the 5G Core (5GC)compared to the EPC is that 5GC's control plane (CP) functions interactin a Service-Based Architecture (SBA). The Network Repository Function(NRF) provides NF service registration and discovery, enabling NFs(network functions) to identify appropriate services within one another.These SBA principles apply to interfaces between CP functions within 5GConly, so for interfaces towards the Radio Access Network (NG-RAN),CPE/FWA or user plane (UP) functions (N1, N2, N3, N4, N6 and N9) areexcluded. 5GC also has functional separation of the Access and MobilityFunctions (AMF) and Session Management Functions (SMF), and alsoincludes the separation of UP (user plane) and CP (control plane)functions of the gateway, which is an evolution of the gateway CP/UPseparation (CUPS) introduced in 3GPP Release 14 for the EPC. Otherdifferences include a separate Authentication Server (AUSF), and severalnew functions, such as the Network Slice Selection Function (NSSF) andthe Network Exposure Function (NEF), each of which can be leveraged bye.g., a network operator such as an MSO/MNO when provisioning servicesto the various CPE/FWA, including in support of ProSe functionsincluding those for relay or supplementation as described herein.

It will be appreciated that while the various embodiments of the presentdisclosure are described in the context of D2D communication providedvia the 3GPP ProSe standards and framework, the present disclosure is inno way so limited, and in fact other D2D or “pseudo-D2D” communicationmodalities (including those which must pass through at least a portionof the MSO/MNO infrastructure supporting the CPE/FWAs) may be usedconsistent with the disclosure to provide the necessary cross-CPE/FWAidentification and communication functionality.

FIG. 8 illustrates one exemplary embodiment of a generalized method 800of using D2D discovery and synchronization protocols according to thepresent disclosure. As shown, in step 802, the out-of-coverage CPE/FWA303 c has to synchronize in time and frequency to the one or morein-coverage CPE/FWA 303 a, 303 b.

Next, per step 804, the discovery protocol is performed. In oneembodiment, a discovery message or request is sent by an advertising(out-of-coverage) CPE to a other CPE in its local area. However, it willbe appreciated that other approaches may be used consistent with thepresent disclosure, including instigation of discovery ofout-of-coverage CPE/FWA by one or more in-coverage CPE/FWA (e.g., usingannouncement or similar protocols), including that directed by thenetwork (e.g., EPC/5GC or another network entity such as an MSO networkcontroller process).

Per step 806, D2D communication via the established channels isperformed.

FIG. 8A illustrates one implementation of the method 800 of FIG. 8 inthe context of 3GPP D2D procedures and protocols. Per step 821 of themethod 820, the CPE/FWA acting as the SyncRef (which, depending onnetwork configuration or conditions as previously described, may beeither the secondary CPE/FWA or a primary CPE/FWA, and these roles mayeven be performed by both types of CPE/FWA to facilitate discoverybetween the devices). In the exemplary embodiment, the secondaryCPE/FWAs are configured to operate as SyncRefs, and hence announcethemselves via the SLSS. Note that Model A or B may be used (Model Abeing basically the “I am here” model, whereas Model B is the “who isthere” type of approach). In some variants, the CPE/FWA may beprogrammed via e.g., firmware to assume one Model or the other oninitial startup (e.g., Model A), but once responding primary CPE/FWA arediscovered and the data relating thereto stored, the device will revertto the Model B approach since it is then aware (presumably) of specificprimary CPE/FWA within range which will respond.

Similarly, the selection of Model A/B may be predicated at least in parton desired latency parameters (e.g., Model B may, when a target primaryCPE/FWA is known, produce faster synchronization and communicationresource allocation, and hence less latency), and/or prior historicalcapacity or bandwidth capability (e.g., if a secondary CPE/FWA has dataindicating that a given primary device is effectively always capable ofmeeting the secondary device's SLA, then the secondary device can targetthat primary device alone via Model B, whereas if the secondary devicehas historically had to contact multiple primary devices to reach itsSLA, it may start out using Model A protocols to identify these multipleconstituents rapidly). Numerous other permutations or combinations ofModel A or B protocols may be used consistent with the presentdisclosure as well, the foregoing being merely exemplary.

Per step 822 of the method 820, D2D synchronization over a Sidelink isperformed, using the previously described PSSS and SSSS. In oneembodiment, the PSSS and SSSS are transmitted in two adjacent SCFDMAsymbols in the same subframe. PSS is transmitted in a first slot of thesubframe, whereas SSSS is transmitted in a second slot of the subframe.Sixty-two subcarriers are used to transmit PSSS, and sixty-twosubcarriers are also used to transmit SSSS.

Next, per step 824, Type 2B UE-specific discovery resource allocation isutilized for the prospective D2D communication session establishment. Aspreviously discussed, this Type is based on a schedule, and in oneembodiment the EPC or 5GC “pushes” a schedule for CPE/FWA discoveryallocation out to the primary CPE/FWA, which then communicates the UE(aka CPE/FWA)-specific schedule to the secondary UE during discovery, Inanother approach, the secondary CPE/FWA obtains the schedule for itselfvia its own firmware (i.e., is pre-programmed to select from a knownpool of resources and schedule (which are also known or otherwiseaccessible to the network and hence the primary CPE/FWA) Lastly, perstep 826 of the method 820, radio resources for direct communication canbe provided by the network (e.g., from EPC or 5GC via xNB) (Mode 1) orselected by the out-of-coverage CPE/FWA autonomously (Mode 2). In theexemplary embodiment, the one or more in-coverage CPE/FWA 303 a, 303 b,being in coverage and in RRC_connected state, can use transmission Mode1, which means the network allocates the exact resource to the primaryCPE. In transmission Mode 1, the one or more in-coverage CPE/FWA 303 a,303 b sends a request requesting use of direct communication. Based onthe requesting information, the xNB can send a grant of resources in anRRC message, which the receiving CPE/FWA 303 a, 303 b can then decode.

FIG. 9 is a ladder diagram illustrating an exemplary embodiment of acommunications protocol used to implement the foregoing methodologies ofD2D communication in support of out-of-coverage services according tothe disclosure. In this embodiment, one or more primary CPE/FWA 303 a,303 b first initiate a request to the network (here, the CBSD/xNB 301)for D2D communication resource allocation. Via the xNB/CBSD, the primaryCPE/FWA(s) receive resource grant and related scheduling instructionsfrom the serving xNB. Using the allocated communication resources, theprimary CPE/FWA signals the secondary CPE (which has already beendiscovered via the D2D discovery and resource allocation protocolspreviously described). This signaling informs the secondary CPE/FWA ofthe network resources (including time-frequency resources) to be usedfor data communication with the serving primary CPE/FWA.

Subsequently, the secondary device 303 c monitors its performance on theinitially granted resources, and if deficient, makes request to theservice xNB/CBSD (via the primary CPE) for additional resources. Thisrequest is evaluated by the network (e.g., EPC or 5GC entity), thelatter which then searches for one or more other registered andsynchronized primary CPE/FWA (i.e., already synchronized or at leastsynchronizable with the secondary CPE), and directs provision ofadditional resources to the secondary CPE via the identified one or moreother primary CPE/FWA using a similar protocol to that used for theinitial primary CPE/FWA.

Packet Management—

In that packet streams for a given recipient (e.g., out-of-coverage)CPE/FWA 303 c must at some level be aggregated and carried across eachof the serving bearers (other CPE/FWA 303 a, 303 b, and the base station301), some mechanism is needed to manage such packet stream aggregation.In one exemplary approach, a transport layer function is used to managepacket allocations across the different bearers. This approachadvantageously obviates any PHY or link-layer modifications, and alsosupports high-throughput so as to maintain QoS and SLA requirements forthe target (out-of-coverage) CPE/FWA 303 c.

FIG. 10 illustrates an example of aggregation of multiple links at thetransport layer of the out-of-coverage CPE/FWA 303 c according to thepresent disclosure. As shown, the exemplary implementation of FIG. 10uses a message-oriented protocol such as the Stream Control TransmissionProtocol (SCTP) for packet bundling and transmission. A typical SCTPpacket 1020 includes a common header 1022 and data chunks 1024 a, 1024 nfrom the respective in-coverage CPEs 303 a, 303 n, which are aggregatedor associated in the transport layer of the recipient out-of-coverageCPE 303 c. Each chunk 1024 a, 1024 n includes a one byte type identifier(with 15 chunk types defined by RFC 4960, incorporated herein byreference in its entirety, and at least 5 more defined by additionalRFCs), flag bits, a chunk length field, and other data which uses theremainder of the chunk.

As a brief aside, Stream Control Transmission Protocol (SCTP) is amulti-stream transport layer protocol that supports multiple independentstreams per logical connection. SCTP allows transmission of severalindependent streams of chunks in parallel to, inter alia, eliminateunnecessary head-of-line blocking and delays caused thereby, as opposedto Transmission Control Protocol (TCP) byte-stream or single-streamdelivery which may delay transmitting data to wait for the possibilityof more data being queued by the application. Additionally, SCTPutilizes multiple redundant paths to, inter alia, increase reliability.SCTP takes advantage of multi-homing, or multiple interface usage, atthe transport layer, to allow a single SCTP association to run acrossmultiple paths (e.g., in the present context, multiple PHY/layer 2connections routed via different primary CPE/FWA).

Hence, in the illustrated embodiment of FIG. 10, the application layerprocess 1010 can utilize application-specific transports and endpointsand via SCTP (including e.g., each of the data connections between thein-coverage and out-of-coverage CPE/FWA 303 a, 303 b, . . . 303 n, aswell as the other serving CPE/FWA), support each of these via commontransport layer functionality. Aggregation of these multiple links isapplied using SCTP at the backhaul (baseband) of the out-of-coverageCPE/FWA 303 c, in effect allowing the CPE/FWA 303 c to act as atransport layer aggregator of (and congestion control process for)multiple streams of chunks 1024 a, 1024 n, including those intended forthe out-of-coverage CPE 303 c yet received via the different airinterface channels.

In one embodiment, the streams from various primary CPE/FWA are combinedusing SCTP at the out-of-coverage CPE 303 c. The reverse is carried outfrom the secondary CPE 303 c towards the (primary) CPE/FWA and theserving base-station(s). Any duplication of packets is in oneimplementation taken care of by the underlying PDCP (packet dataconvergence protocol) of LTE (i.e., TS 25.323 and related).

FIG. 10A illustrates one exemplary generalized method 1050 of packetmanagement over multiple bearers according to the present disclosure. Asshown, in step 1052, the out-of-coverage CPE/FWA 303 c receives packetsassociated with one of its streams or flows (e.g., associated with anapplication layer process 1010) from an in-coverage CPE/FWA 303 a, 303b, via the air interface channels established with that device. Per step1054, it also receives packets from another CPE/FWA 303 a, 303 b, viathe air interface channels established with those devices.

At step 1056, the recipient out-of-coverage CPE/FWA aggregates thepackets from all sources at its backhaul transport layer (e.g., usingthe SCTP protocol), and optionally applies congestion and flow controlper step 1058 so as to optimize the backhaul as a “virtual unified”transport (e.g., via balancing of the individual constituents associatedwith the respective bearers of the serving primary CPE/FWA).

FIG. 11 is a functional block diagram illustrating the one embodiment ofan exemplary SCTP endpoint architecture 1100 according to the presentdisclosure. In FIG. 111, data chunks 1024 associated with multiplelinks/connections (e.g., those received from multiple different primaryCPE via their respective PHY connections to the recipient secondary CPE)are aggregated at the SCTP layer into a single SCTP packet 1020.Demultiplexing is also utilized to, inter alia, route packets associatedwith different destination ports to their proper application within theapplication layer.

Conversely, for transmission, different packets associated withdifferent applications on the endpoint (e.g., secondary CPE/FWA) aresent to their target endpoints (e.g., an IP address of a distantprocess) by being routed via respective sockets 1102 to the mux processof the SCTP layer, whereby they are logically bundled or aggregated atthe transport layer, and then transmitted to the network layer (IP) fortransmission via the lower layers of the stack (which here, includemultiple distinct “links”).

In an alternate embodiment, the Transmission Control Protocol (TCP)packets from e.g., the respective primary CPEs 303 a, 303 b areaggregated in the recipient secondary CPE 303 c based on use ofMulti-path Transmission Control Protocol (MPTCP) 823. As a brief aside,MPTCP allows a Transmission Control Protocol (TCP) connection to usemultiple paths to, inter alia, maximize resource usage and increaseredundancy. These features enable inverse multiplexing of resources, andhence in theory increases TCP throughput to the aggregate of allavailable link-level channels (as opposed to a single one as required bynon-MPTCP implementations based on standard TCP). Additionally,link-level channels may be added or dropped, such as where a givenCPE/FWA begins or ceases service or supplementation of a secondaryCPE/FWA in the present context, without disrupting the end-to-end TCPconnection between e.g., the served CPE/FWA and a remote network serversuch as a content or web server. Link handover is handled by abstractionin the transport layer, without change to the network or link layers.Accordingly, link handover and instantiation/teardown can be implementedat the endpoints of the TCP session (e.g., the CPE/FWA) withoutrequiring special functionality in the supporting sub-networkinfrastructure. Multipath TCP can balance a single TCP connection acrossmultiple interfaces to achieve a desired throughput.

However, in certain use cases, scalability of MPTCP may be limited, suchas by considerations relating to addressing; e.g., when there are morethan two addresses for a given end point. This may be the case forinstance for out-of-coverage CPEs, such as where more in-coverage CPE toout-of-coverage CPE connections are anticipated or used on average (asopposed to in-coverage CPE to in-coverage CPE connections).

Inter-Process Protocol—

FIG. 12 is a ladder diagram illustrating the communication flow forproviding quasi-licensed wireless service including IP data packetsto/from an out-of-coverage CPE/FWA via one or more in-coverage CPE/FWAin accordance with the exemplary methods of FIGS. 4-5B.

In the embodiment illustrated in FIG. 12 (based on a 3GPP LTEinfrastructure), the communication protocol 1200 includes the “incoverage” or serving CPE/FWAs 303 a, 303 b (see FIG. 3A) firstperforming initial attach procedures with the relevant E-UTRAN/EPCentities (including the P-GW packet gateway 709) via their respectiveserving eNBs 301 (steps 1 a and 1 b).

Next, D2D discovery of the type previously described between theout-of-coverage CPE/FWA 303 c and the CPE/FWA of the other premises 303a, 303 b is performed (such as via unlicensed or GAA spectrum), andafter discovery and resource allocation, supporting functions such as IPaddress discovery and device authentication/negotiation are performed,as shown in FIG. 12 (steps 2 a-5 b). As previously noted, the variousD2D processes may be “push” or “pull” from any node to any other,depending on how the protocol is configured (e.g., the out-of-coverageCPE/FWA may periodically instigate the discovery and request forresources, or alternatively one of the high-TP CPE/FWA devices may(after discovery and D2D connection establishment) periodically pollother CPE/FWA (including the out-of-coverage CPE/FWA) to cause thelatter to evaluate their TP (e.g., versus their relevant SLA) and reportback to the polling device.

It will be appreciated that the D2D discovery and connection process ofsteps 2 a-5 b may also take several different forms, depending on theparticular functionality desired. For instance, in one approach,discovery and connection with all available prospective primary CPE/FWAis established irrespective of whether the out-of-coverage CPE/FWA 303 cwill utilize them; the various discovered and connected CPE/FWA willevaluate their own ability to relay (as previously described withrespect to e.g., FIGS. 4A-5B), and either the requesting CPE/FWA 303 cor the relaying (primary) CPE/FWA 303 a, 303 b will decide which of theconnected population are ultimately utilized, such as based ondirectives from the EPC.

Alternatively, in another approach, more serialized logic is utilized,such as where the connection and evaluation of each prospective primaryCPE/FWA is conducted before any further D2D connections to other CPE areestablished. For instance, if the first “connected” CPE/FWA is capableof providing complete resources to the out-of-coverage CPE/FWA (e.g., upto its SLA) as determined by e.g., the EPC, then no furthercommunication is required with other potential primary CPE/FWA. Thisapproach has the advantage of lower processing overhead and simultaneousradiated interference from the participating CPE (e.g., as opposed to a“broadcast” or other such model), yet may also introduce additionallatency in reaching full SLA resources for the out-of-coverage CPE/FWA.

In yet another approach, the out-of-coverage CPE/FWA 303 c may accesshistorical or even predictive/speculative data regarding one or moreknown primary CPE/FWA (e.g., captured via prior sessions between thedevices, or via a download of such data from one or more of the MSO orMNO core entities), and use this data to make an “educated guess” as towhich primary CPE/FWA is likely to be the optimal choice for relaying(e.g., which CPE/FWA or grouping thereof has historically provided, oris projected to provide, complete resources with the minimum ofoverhead. For example, if one nearby CPE/FWA has historically alwaysbeen able to provide complete SLA resources to the out-of-coverageCPE/FWA 303 c by itself, then this is an obvious first choice. As such,the present disclosure contemplates that each CPE/FWA may build its own(or be provided with) a hierarchy or “logic tree” to be applied to theD2D logic of steps 2 a-5 b in FIG. 12.

Note that as previously indicated, the foregoing type of gating orselection can (i) be applied at the D2D discovery phase; i.e., asecondary CPE/FWA may selectively only initiate D2D discovery andresource allocation procedures with a subset of potential primarydevices based on prior data or knowledge, or (ii) afterdiscovery/communication establishment is complete, such that thesecondary CPE can obtain actual (then current) TP/iPerf data on which tobase its selection of a primary CPE. Moreover, in the EPC-based model,primary CPE/FWAs can provide their then-current TP/iPerf data to the EPCwhich can generate its own logic tree or hierarchy for any subsequentrequests from secondary CPE for supplementation (e.g., based on a given“live” time window and associated geographic area). As such, the EPC can“pre-load” certain primary CPE to immediately respond as suitablecandidates for any incipient secondary CPE requests received within thewindow, including also possibly allocating PAL or cleaner spectrum tosuch primary CPE). This approach may also be utilized in conjunctionwith the foregoing “targeted” secondary CPE discovery and connectionprocedures; e.g., such as where a pre-loaded primary CPE (which ineffect always responds to the service requests of a given secondary CPEunless it is incapable of doing so) is also used by the secondary CPE asits first or priority (“go-to”) CPE for D2D discovery.

It will also be appreciated that the foregoing decisions/logic may behanded off to another network entity or process, such as logic withinthe P-GW 709, or even another MNO or MSO entity or controller, includinge.g., the ProSe server when so equipped.

Per steps 6 a-6 b of FIG. 12, the participating (primary) CPE/FWA 303 a,303 b then contact the cognizant spectrum allocation process (e.g., theSAS 717 for CBRS implementations), such as via an MSO-based orthird-party domain proxy (DP)—not shown, to request a spectrum grant toenable bandwidth relaying to the requesting out-of-coverage CPE/FWA 303c. Per CBRS protocol, the SAS registers the devices (itself as a CBSD,and the secondary CPE as a non-CBSD FWA) and returns the respectivegrant(s) to each requester 303 a, 303 b, thereby enabling establishmentof wireless connection (e.g., RRC Connected state) via the primary airinterface of each CPE/FWA (i.e., within the 3.550-3.70 GHz band using3GPP LTE or NR protocols).

It is noted that the D2D discovery and connection protocols of steps 2a-5 b are in one embodiment conducted using a “sidelink” (e.g., theSidelink as specified in Rel. 12-14), or another alternate channel whichmay be available for such purposes. In one embodiment, the system(granted) frequency utilized by the in-coverage CPE/FWA is used forpurposes of the D2D/sidelink communications, although it will beappreciated that other frequencies or bands may be used consistent withthe present disclosure. The sidelink frequency can also be indicated inthe grant. In FIG. 12, the primary CPE/FWAs are requesting permissionfrom the SAS for “xNB-like operation” to support the out-of-coverageCPE.

CBRS FWA Apparatus—

FIG. 13 illustrates one exemplary embodiment of a CPE/FWA 303 (e.g.,roof-mounted FWA with associated radio head and CPE electronics)configured according to the present disclosure.

It will be recognized that while described generically, the apparatus ofFIG. 13 is readily adapted for use as either a primary or a secondaryCPE, and in fact, the present disclosure contemplates configurationswhere each CPE/FWA in a given network or network portion are configuredto be able to operate as both a primary and secondary CPE/FWA dependingon application or operational context. For instance, a given secondaryCPE 303 c may, upon availability of a new xNB installed or turned onnearby, may then become “in network” and act as a primary CPE/FWA 303 a.Rather than maintain two heterogeneous hardware/software/firmwareconfigurations and logistics/supply chains therefore, it may be mosteffective to simply provide all customers/installations with a “stemcell” CPE/FWA which can readily assume either role depending on itsparticular circumstance.

It will also be appreciated that while described in the context of aCBRS-compliant FWA, the device of FIG. 13 may be readily adapted toother spectra and/or technologies such as e.g., Multefire, DSA, LSA, orTVWS.

As shown in FIG. 13, the CPE/FWA is a Node Manager (NM)- andProSe-enabled device which includes, inter alia, a processor subsystemwith CPU 1342, a memory module 1354, one or more radio frequency (RF)network interface front ends 1348 (e.g., adapted for operation in the3.55-3.70 GHz band, C-Band, NR-U bands, etc.) and associated antennaelements 1355, one or more backend interfaces (e.g., USB, GbE, etc.), aWLAN/BLE module 1324 with integrated WLAN router and antennae 1356,power module 1352 (which may include the aforementioned PoE injectordevice), and an RF baseband processing module 1356.

In one exemplary embodiment, the processor subsystem 1342 may includeone or more of a digital signal processor (DSP), microprocessor (e.g.,RISC core(s) such as ARM core), field-programmable gate array, GPU, orplurality of processing components mounted on one or more substrates(e.g., printed circuit board). The processor subsystem/CPU 1342 may alsocomprise an internal cache memory (e.g., L1/L2/L3 cache). The processorsubsystem is in communication with a memory subsystem 1354, the latterincluding memory which may for example comprise SRAM, flash, and/orSDRAM components. The memory subsystem may implement one or more ofDMA-type hardware, so as to facilitate data accesses as is well known inthe art. The memory subsystem of the exemplary embodiment containscomputer-executable instructions which are executable by the processorsubsystem.

In this and various embodiments, the processor subsystem/CPU 1342 isconfigured to execute at least one computer program stored in programmemory 1354 (e.g., a non-transitory computer readable storage medium). Aplurality of computer programs/firmware are used and are configured toperform various functions such as communication with relevant functionalmodules within the CPE/FWA 303 such as the radio head and WLAN/BLEmodule 1324.

Various other functions useful for and typical in “radio head”electronics including baseband management (e.g., transmit and receivefunctions via the baseband processor 1356 and associated Tx and Rxchains of the RF front end 1348. For example, in one embodiment, the Txand Rx chains are part of an RF front end used for OFDM-based RFcommunication with CBSD devices (e.g., xNB 301 operating as CBRS basestations deployed by the MSO or a third party, so as to providebackhaul).

In the exemplary embodiment, the memory subsystem 1354 includes a NodeManager (NM) process or logic module 1321 configured to supportout-of-coverage service provision functionality and protocols such asthose described according to FIGS. 3A-5B. For instance, in oneimplementation (secondary CPE/FWA role), the NM 1321 includes thenecessary logic and functionality to (i) access data within e.g., memory1354 or the mass storage device relating to known other CPE/FWA 303;(ii) if no other CPE/FWA are known a priori to the out-of-coverageCPE/FWA, initiate a search (e.g., via D2D discovery protocols) for thesame; (iii) establish a D2D connections to one or more of the otherCPE/FWA; (iv) request data/bandwidth from the other device(s); and (v)determine during operation if the CPE/FWA TP is lower than a prescribedSLA (e.g., via an installed iPerf client 317) and if so, requestsupplementation from another primary CPE as in FIG. 12.

The NM logic 1321 may also be configured to enable different D2D rolesor modes for the device, even within the same context (e.g., as aprimary or secondary CPE). For instance, in one configuration, the NMlogic 1321 may allow a device 303 to operate either in Model A or B,Type 1 or 2B, and/or Mode 1 or 2 D2D configurations as previouslydescribed depending on operational conditions, primary context (i.e.,being “in network” or “out-of-network”), network policies or rules, orany number of other factors.

Moreover, since the physical channel dynamics for a given CPE/FWA maychange over time (whether increase or decrease) such as due to new xNBinstall or extant xNB removal, growth of trees, introduction of otherinterferers, etc. over time, each CPE/FWA 303 installed is in theexemplary embodiment configured to enable dynamic switching between aseither a receiving device (i.e., out-of-coverage device) or a provider(i.e., in-coverage or high-TP device) at any given time as previouslynoted, and/or dynamic D2D protocol switching (e.g., from Type 2B to Type1).

Additionally, the present disclosure contemplates utilization of e.g.,primary CPE/FWA 303 a in conjunction with other relay or supplementationfunctions, including those described in co-owned and co-pending U.S.patent application Ser. No. 16/676,188 filed Nov. 6, 2019 and entitled“METHODS AND APPARATUS FOR ENHANCING COVERAGE IN QUASI-LICENSED WIRELESSSYSTEMS,” incorporated herein by reference in its entirety. Forinstance, a primary CPE 303 a may both (i) supplement another “innetwork” (but low TP) CPE/FWA 303 b, and (ii) provide service to anout-of-network CPE 303 c. As another example, in cases where the high-TPprimary CPE is limited and can only feasibly support eithersupplementation of another primary CPE or provision of services to asecondary CPE (including putatively some with no service to begin with),the logic of the NM 1321 may cause the high-TP CPE to alwayspreferentially service the secondary CPE. Various other possible servicescenarios and combinations of primary/secondary CPE use cases andapplications will be appreciated by those of ordinary skill given thepresent disclosure.

As shown, the CPE/FWA 303 also includes the previously described ProSelogic module 1323 for 3GPP D2D communication support, as well as STCPstack logic 1327 to implement e.g., the packet management and relatedfunctions (including STCP packet aggregation and mux/demux) as describedwith respect to FIGS. 10-11.

Service Provider Network—

FIG. 14 illustrates one embodiment of a service provider networkconfiguration useful with the out-of-network service provisionfunctionality and supporting 3GPP/CBRS-based wireless network(s)described herein. It will be appreciated that while described withrespect to such network configuration, the methods and apparatusdescribed herein may readily be used with other network types andtopologies, whether wired or wireless, managed or unmanaged.

The exemplary service provider network 1400 is used in the embodiment ofFIG. 14 to provide backbone and Internet access from the serviceprovider's wireless access nodes (e.g., CBSD/xNBs, Wi-Fi APs, FWAdevices or base stations operated or maintained by the MSO), and one ormore stand-alone or embedded cable modems (CMs) 1433 in datacommunication therewith.

The individual xNBs 301 are backhauled by the CMs 1433 to the MSO corevia e.g., CMTS or CCAP MHAv2/RPD or other such architecture, and the MSOcore 1450 includes at least some of the EPC/5GC core functionspreviously described, as well as the ProSe Application Server as shown.Each of the primary CPE/FWA 303 a, 303 b are communicative with theirrespective xNBs 301, as well as potentially secondary CPE/FWA as neededto support the relay/service provision functions previously described.Client devices 1406 such as tablets, smartphones, SmartTVs, etc. at eachpremises are served by respective WLAN routers 323, the latter which arebackhauled to the MSO core or backbone via their respective CPE/FWA.

Notably, in the embodiment of FIG. 14, all of the necessary componentsfor support of the OON service functionality are owned, maintainedand/or operated by the common entity (e.g., cable MSO). The approach ofFIG. 14 has the advantage of, inter alia, giving the MSO completecontrol over the entire service provider chain, including control overthe xNBs so as to optimize service to its specific customers (versus thenon-MSO customer-specific service provided by an MNO), and the abilityto construct its architecture to optimize incipient 5G NR functions suchas network slicing, gNB DU/CU Option “splits”, etc.

In contrast, in the embodiment of FIG. 15, the architecture 1500 isdivided among two or more entities, such as an MNO and an MSO. As shown,the MSO service domain extends only to the CPE/FWA and served premisesand the MSO core functions, while other functions such as 3GPPEPC/E-UTRAN or 5GC and NG-RAN functionality is provided by one or moreMNO networks 1532 operated by MNOs with which the MSO has a serviceagreement. In this approach, the ProSe Application server is stillmaintained and operated by the MSO (since the MSO maintains cognizanceover the CPE/FWA which must communicate via ProSe), although this is nota requirement, and the present disclosure contemplates embodiments wherethe ProSe function is maintained by the MNO or even a third party. Theapproach of FIG. 15 has the advantage of, inter alia, avoiding moreCAPEX by the MSO, including duplication of infrastructure which mayalready service the area of interest, including reduced RF interferencedue to addition of extra (and ostensibly unnecessary) xNBs or othertransceivers.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

1.-20. (canceled)
 21. Computerized premises apparatus for use in a wireless network, comprising: at least one wireless interface; processor apparatus in data communication with the at least one wireless interface; and storage apparatus in data communication with the processor apparatus, the storage apparatus comprising at least one computer program configured to, when executed by the processor apparatus: engage in communication with at least one wireless access device via utilization of a synchronization and discovery protocol, the at least one wireless access device within a wireless range of (i) the at least one wireless interface of the computerized premises apparatus and (ii) at least one base station; obtain first data from the at least one wireless access device enabling establishment of a first wireless connection, the first wireless connection between the computerized premises apparatus and the at least one wireless access device; utilize the at least one wireless access device to request a resource grant using the at least one base station; and based at least on a criterion relating to at least one of a performance or capability of the at least one wireless access device being exceeded, receive resources in accordance with the resource grant from the at least one wireless access device.
 22. The computerized premises apparatus of claim 21, wherein the computerized premises apparatus and the at least one wireless access device each comprise a FWA (fixed wireless access) device configured to operate in a CBRS (citizens broadband radio service) frequency band, and the at least one base station comprises a 3GPP-compliant NodeB (NB) configured to operate in a CBRS frequency band.
 23. The computerized premises apparatus of claim 21, wherein the at least one computer program is further configured to, when executed by the processor apparatus: determine that the first connection cannot meet a prescribed performance level requirement associated with the computerized premises apparatus based on the resources received from the at least one wireless access device; and based at least on the determination, cause a communication with at least one second wireless access device within wireless range of the computerized premises device to request supplementation of the wireless connection via a second wireless connection, the communication to request supplementation comprising data relating to an amount of bandwidth supplementation required by the computerized premises apparatus.
 24. The computerized premises apparatus of claim 23, wherein the at least one computer program is further configured to, when executed by the processor apparatus: utilize a transport layer process to enable aggregation of data packets transmitted to the computerized premises apparatus via the wireless connection and the second wireless connection when the wireless connection and the second wireless connection have been established.
 25. The computerized premises apparatus of claim 23, wherein the determination that the first connection cannot meet the prescribed performance level requirement associated with the computerized premises apparatus comprises determination of the amount by a performance determination process operative to execute on the computerized premises apparatus, the determination process configured to measure at least one parameter related to data rate or throughput of the at least one wireless interface while utilizing the wireless connection.
 26. The computerized premises apparatus of claim 21, wherein the engagement comprises utilization of a 3GPP D2D (Device to Device) protocol based on a schedule provided to at least the at least one wireless access device by the at least one base station.
 27. The computerized premises apparatus of claim 21, wherein the engagement comprises utilization of a 3GPP D2D (Device to Device) protocol based on a discovery protocol initiated by the computerized premises apparatus.
 28. Computer readable apparatus comprising a non-transitory storage medium, the non-transitory medium comprising at least one computer program having a plurality of instructions, the plurality of instructions configured to, when executed on a processing apparatus, cause a computerized apparatus to: receive first data relating to a measurement of at least one first performance metric relating to a first wireless connection between a first computerized premises apparatus and a first base station, the first wireless connection used to provide first resources to the first computerized premises apparatus; based on the at least one performance metric exceeding a first prescribed threshold, cause establishment a second wireless connection between the first computerized premises apparatus and a second computerized premises apparatus, the second wireless connection utilized for a provision of second resources to the second computerized premises apparatus.
 29. The computer readable apparatus of claim 28, wherein the plurality of instructions are further configured to, when executed on the processing apparatus, cause the computerized apparatus to: receive second data relating to a measurement of at least one performance metric relating to the second wireless connection; receive third data relating to a measurement of at least one performance metric relating to a third wireless connection between a third computerized premises apparatus and either the first base station or a second base station; and based at least on (i) the second data indicating that the at least one second performance metric does not meet a second prescribed threshold, and (ii) the third data indicating that the at least one performance metric exceeds a third prescribed threshold, cause establishment of a fourth wireless connection between the first computerized premises apparatus and the third computerized premises apparatus, the fourth wireless connection utilized for a provision of third resources to the second computerized premises apparatus, the third resources supplementing the first and second resources such that the least one second actual performance metric at least meets the second prescribed threshold.
 30. The computer readable apparatus of claim 29, wherein the second data relating to the measurement of the at least one performance metric relating to the second wireless connection comprises data relating to at least Stream Control Transmission Protocol (SCTP) packet performance.
 31. The computer readable apparatus of claim 28, wherein: the second computerized premises apparatus comprises an FWA device that is (i) completely out of a coverage area of the first and second base stations and (ii) configured to operate in a CBRS (Citizens Broadband Radio Service) frequency band; the first and second base stations each comprise a 3GPP-compliant NodeB (NB) configured to operate in a CBRS frequency band; and each of the wireless connections each comprise operation in an RRC_Connected state.
 32. The computer readable apparatus of claim 28, wherein the plurality of instructions, the plurality of instructions configured to, when executed on the processing apparatus, cause the computerized apparatus to: receive data representative of at least one message relating to a request for a spectrum allocation for use in establishing the second wireless connection; wherein the computer readable apparatus comprises a computerized spectrum allocation process and the at least one message is received via a communication session with at least one computerized process within a managed wireless network serving the first computerized premises apparatus, the communication session configured to enable transmission of the data representative of the at least one message from the second computerized premises apparatus and via the first computerized premises apparatus.
 33. A computerized method of utilizing one or more fixed wireless access (FWA) devices within a wireless network, the computerized method comprising: causing discovery of a first FWA device that is at least one of a) outside a coverage area of the wireless network, or b) at an edge of the coverage area; causing transmission of data associated with at least one of (i) the first FWA device, or (ii) at least one second FWA device, to at least one computerized resource allocation process, the at least one computerized resource allocation process configured to grant an amount of resources to the first FWA device via use of the at least one second FWA device; and based on receipt of the grant of the amount of the resources from the at least one computerized resource allocation process, providing the amount of the resources to the first FWA device via the at least one second FWA device, thereby connecting the first FWA device to the wireless network via the at least one second FWA device.
 34. The computerized method of claim 33, further comprising establishing a 3GPP (Third Generation Partnership Project) D2D (device to device) protocol connection with the first FWA device based at least on the discovering thereof.
 35. The computerized method of claim 33, further comprising identifying of the at least one second FWA device within the coverage area of the wireless network and capable of providing the resources to the first FWA device, the identifying comprising determining that a data rate associated with the at least one second FWA device exceeds a prescribed service level agreement (SLA) requirement, the SLA requirement between a subscriber of a network operator managing the wireless network and the network operator.
 36. The computerized method of claim 33, further comprising identifying of the at least one second FWA device within the coverage area of the wireless network and capable of providing the resources to the first FWA device, the identifying comprising use of data relating to a proximity of the at least one second FWA device to one or more base station apparatus within the wireless network, such that at least one of (i) maximal impact or (ii) relay performance, is enabled with respect to a largest possible number of other FWA devices that are outside the coverage area of the wireless network.
 37. The computerized method of claim 33, wherein: the causing transmission of the data to the computerized resource allocation process comprises causing transmission of a first performance level associated with a primary second FWA device to a first computerized resource allocation process, and causing transmission of a second performance level associated with a secondary second FWA device being served by the primary second FWA device to a second computerized resource allocation process; and the grant of the amount of the resources from the at least one computerized resource allocation process comprises a grant of resources from a priority access license (PAL) spectrum to the primary second FWA device, and a grant of resources from a general authorized access (GAA) spectrum to the secondary second FWA device.
 38. The computerized method of claim 33, wherein the causing of the discovery of the first FWA device comprises: causing at least one of the first FWA device or the at least one second FWA device to transmit an announcement, the announcement configured to indicate to other FWA devices that the at least one of the first FWA device or at least one second FWA device exists; and based on the announcement by and receipt of at least one response thereto, causing the first FWA device to send data to the at least one second FWA device to cause establishment of a wireless connection therebetween.
 39. The computerized method of claim 33, wherein the causing of the transmission of the performance data to the at least one computerized resource allocation process comprises causing the request to be transmitted from the first FWA device to the at least one computerized resource allocation process via the at least one second FWA device utilizing a sidelink connection between the first FWA device and the at least one second FWA device.
 40. The computerized method of claim 33, wherein the providing the amount of the resources to the first FWA device via the at least one second FWA device comprises repurposing a device-to-device connection between the first FWA device and the at least one second FWA device to supplement resources of the first FWA device from at least one second FWA device such that a performance metric associated with the first FWA device at least meets a prescribed threshold. 